version 0.4.0 crashes when using developer tools

[JBaron]

When I open the developers tool, set a break point and start debugging, my node-webkit instance crashes as soon as it reaches the break-point. Not sure if related, but also when I open the developers tools, since version 0.4.0 all the icons at the menu-bar have gone. When I run the same app in 0.3.7 everything goes fine.

My environment is Ubuntu-12.04/32bits.

Are there any local directories that node-webkit uses that I need to clean up when installing a new version?

//Peter

[Roger WANG]

JBaron <pe...@jbaron.com> writes:

> When I open the developers tool, set a break point and start debugging, my
> node-webkit instance crashes as soon as it reaches the break-point.

Could you please provide examples and steps so I can reproduce it here.

> Not sure if related, but also when I open the developers tools, since
> version 0.4.0 all the icons at the menu-bar have gone. When I run the
> same app in 0.3.7 everything goes fine.

I'll see the icon issue.

>
> My environment is Ubuntu-12.04/32bits.
>
> Are there any local directories that node-webkit uses that I need to clean
> up when installing a new version?

No. If there is we'll say it in the release notes.

--
Roger WANG Intel Open Source Technology Center

[JBaron]

(forgot to reply to the Google group, so hereby again)

Sure (although this requires a few steps):

1) Clone my CATS project from github (git clone https://github.com/jbaron/cats.git)
2) Start it with node webkit version 0.4.0 (I guess you don't need instructions here ;)
3) Start developers tools: "Help -> Developers Tool"
4) In the developer tools go to "Sources"
5) Select main.js as the source
6) Set a breakpoint on line 586, should read something like Cats.mainEditor.setTheme(theme);
7) Now change the theme so you'll hit the breakpoint you just set: Window -> Theme -> Eclipse
8) Watch the crash

Hope this helps

// Peter

[Frank Hale]

I've followed your steps and I can confirm the crash you are talking about happens to me as well. I'm on Windows 7 x64 and using node-webkit 0.4.0.

--
 
 

[Roger WANG]

JBaron <pe...@jbaron.com> writes:

> (forgot to reply to the Google group, so hereby again)
>
> Sure (although this requires a few steps):
>
> 1) Clone my CATS project from github (git clone
> https://github.com/jbaron/cats.git)
> 2) Start it with node webkit version 0.4.0 (I guess you don't need
> instructions here ;)
> 3) Start developers tools: "Help -> Developers Tool"
> 4) In the developer tools go to "Sources"
> 5) Select main.js as the source
> 6) Set a breakpoint on line 586, should read something like Cats.mainEditor.
> setTheme(theme);
> 7) Now change the theme so you'll hit the breakpoint you just set: Window
> -> Theme -> Eclipse
> 8) Watch the crash

Thanks. I'm able to reproduce it here with 0.4.0 and will fix it. You
can track it here: https://github.com/rogerwang/node-webkit/issues/396

Another question is: is the code supposed to be stopped at main.js:586
when you try to change the theme from the menu? I tried with 0.3.7 it
doesn't crash but the breakpoint is not effective.

[Frank Hale]

I don't have much to offer but I did try this out. I also tried to set breakpoints and they were never effective (eg. the debugger never triggered the breakpoint). Not sure what was going on there. I played with it for about 1 hour.

--

You received this message because you are subscribed to the Google Groups "node-webkit" group.
To unsubscribe from this group, send email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Peter@JBaron]

Good to hear that you were also able to reproduce this.

That method is actually not yet being used in the master branch (my
mistake). So pay no attention to the debugger not stopping over there. I
did however notice in the past that behavior in the past a few times.
Once I have such a case again I'll let you know (However I suspected it
to be more of a bug in the developers tools than in node-webkit).

// Peter