Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Crash, how to debug? #495

jonaslund opened this Issue · 7 comments

4 participants


Crashing within a minute when using and setting/getting the window.location.href through the gui

OS: Mac OS X 10.7.4 – 10.7.5
Node-webkit: 0.4.2
Node: 0.8.11


var gui = require('nw.gui');

 onload = function() {
  process.mainModule.exports.gui = gui;

node-main script

var http = require("http"),
    io = require(''),
    socket = io.connect('', {reconnect: true});

exports.getGui = function() { 
  var gui = exports.gui;

  gui.Window.get().on('loaded', function() {
     var win = thegui.Window.get().window;

     if(win) {
       var currentUrl = win.location.href;

       socket.emit("sendUrl", {url: currentUrl});         

And here's the crash report

Process:         node-webkit [66360]
Path:            /Applications/
Version:         26.0.1377.0 (1377.0)
Code Type:       X86 (Native)
Parent Process:  zsh [62061]

Date/Time:       2013-03-02 13:04:21.882 +0100
OS Version:      Mac OS X 10.7.4 (11E2705)
Report Version:  9

Interval Since Last Report:          9896768 sec
Crashes Since Last Report:           133
Per-App Interval Since Last Report:  5682 sec
Per-App Crashes Since Last Report:   17
Anonymous UUID:                      47A42793-E447-452F-AC01-EE13A207ADA9

Crashed Thread:  0  CrBrowserMain  Dispatch queue:

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000058

VM Regions Near 0x58:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Applications/
    VM_ALLOCATE            0000000000001000-00000000000fb000 [ 1000K] ---/--- SM=NUL  

Application Specific Information:
objc[66360]: garbage collection is OFF

I suspect it has something to do with May I ask why you are using Socket.IO over the default TCP/UDP socket implementation in NodeJS?


There was a bug in pre 10.7.5 that caused all sorts of issues with chromium. If you upgrade it should be fine.

@jonaslund as the server side of the app relies on it, and it's imho the best solution for implementing websockets with nodejs. I'll get on the upgrade and see if it solves the crashes. But it's still not an optimal solution, as users on below 10.7.5 would have a crashing app.

Would be nice, if possible, with better error reporting from node-webkit on crash. something more than a 'EXC_BAD_ACCESS', which is pretty hard to debug.


I have no idea if it is Socket.IO that is causing the crash, but it makes sense that it would be.


After an update to 10.7.5, the crash problem still persists and with the part disabled from the app, it still crashes, so can't see how it makes sense that it's that's causing it.

Is there any way of debugging the crash problem besides the crash log?


Are you still see this with 0.5.1? Could you please provide a test case?


Don't see the problems anymore since 0.6.2 so I'll close it for now. If they reappear I'll revisit this.

@jonaslund jonaslund closed this
@jonaslund jonaslund changed the title from Crash, how to debug? to Crash, how to debug?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.