consistent crashing

7 views
Skip to first unread message

fuhol...@gmail.com

unread,
Feb 21, 2014, 11:09:17 PM2/21/14
to node-...@googlegroups.com
Hello, I recently upgraded node-webkit to 0.9.1 (and tested on 0.9.2 just now), and I keep having a problem where if there's an uncaught exception, nw switches to the cloudy nodejs page error, which is annoying because refreshing back from that page is unreliable at best. If I use process.on(uncaughtException...) nw flat out crashes. This is on something as simple as referencing an undefined local variable. Is this expected behavior?

Prior to using 0.9.1, I've never had these problems. If there was an uncaught exception, it just stated so in the console. No redirecting to cloudy page, no crashing. Just refresh to start anew.

Forgive me as I'm not terribly familiar with node-webkit's underpinnings, it's just really frustrating considering it worked perfectly before.

Also, this is on Windows 8.1 if that helps.

I appreciate any insight you guys can give me.

ilian.sa...@gmail.com

unread,
Feb 23, 2014, 4:18:53 PM2/23/14
to node-...@googlegroups.com, fuhol...@gmail.com
I can confirm this behaviour on linux/ubuntu 64bit.

fuhol...@gmail.com

unread,
Feb 28, 2014, 11:06:51 PM2/28/14
to node-...@googlegroups.com, fuhol...@gmail.com
Anyone have any ideas?

VoidVolker

unread,
Mar 1, 2014, 12:36:32 AM3/1/14
to node-...@googlegroups.com, fuhol...@gmail.com
No. I have the same error few times.

Chris Turnbull

unread,
Mar 1, 2014, 8:01:32 AM3/1/14
to node-...@googlegroups.com, fuhol...@gmail.com
Lots of people have reported this problem.

Turns out there's a simple way to disable it: https://github.com/rogerwang/node-webkit/issues/1218

That said, you'll probably only want to disable it whilst in development.

fuhol...@gmail.com

unread,
Mar 1, 2014, 3:08:22 PM3/1/14
to node-...@googlegroups.com, fuhol...@gmail.com
Chris, thanks for the link. That definitely helped me understand the problem better.

Noticed something rather interesting. In the standard development node-webkit, there are two refresh buttons, one on the left, the other on the right, next to the debugger button. If I use the process.on exception handling, and click refresh on the LEFT button: immediate crash. If I do the same, only with the RIGHT button, it works as intended: no crash, just error log in console.

Can anyone explain that? Seems so bizarre haha.


On Friday, February 21, 2014 8:09:17 PM UTC-8, fuhol...@gmail.com wrote:

VoidVolker

unread,
Mar 1, 2014, 3:16:52 PM3/1/14
to node-...@googlegroups.com, fuhol...@gmail.com

fuhol...@gmail.com

unread,
Mar 1, 2014, 9:21:08 PM3/1/14
to node-...@googlegroups.com, fuhol...@gmail.com
That's really useful. Thanks for that. Unfortunately, doing the reload this way causes the crashes on exceptions.

On Saturday, March 1, 2014 12:16:52 PM UTC-8, VoidVolker wrote:
Reply all
Reply to author
Forward
0 new messages