Version 0.4.0 app crashing on Mac OS X 10.7.5 (4gb ram) EXC_BAD_ACCESS (SIGBUS)

7 views
Skip to first unread message

Rob Righter

unread,
Jan 31, 2013, 11:46:43 AM1/31/13
to node-...@googlegroups.com
Hello,

I have been getting crash reports from users with the exception type: "EXC_BAD_ACCESS (SIGBUS)"

Currently I have a small user base that have macs of various versions of OSX. The crash reports tend to be coming from users with macbook air's running Mac OS X 10.7.5 (4gb ram).

I have attached 2 crash reports.

Has anyone seen this issue? Is it a known problem?

Many Thanks,
Rob


crash-report-1.txt
crash-report-2.txt

Roger WANG

unread,
Jan 31, 2013, 8:39:25 PM1/31/13
to Rob Righter, node-...@googlegroups.com
Hi Rob,

It's not known bug. Did you see any reports on other OSX versions? And
could you please provide something so I can reproduce it here?

Thanks in advance.

--
Roger WANG Intel Open Source Technology Center

Rob Righter

unread,
Feb 1, 2013, 1:37:03 PM2/1/13
to node-...@googlegroups.com, Rob Righter
Hi Roger,

Currently nobody has seen this issue on other os versions, but that might be more a function of my users and less about the bug. There are a number of 10.8 users (including myself) that run the app all day and none of them have had the issue. The issue happens very rarely and Unfortunately I cannot reproduce this issue reliably. The bug reports all have one thing in common, the crash occurs when a desktop notification is being shown, hidden or clicked. I made a quick demo showing how the desktop notifications work. They use a frameless window:

Since you have a better understanding of how multiple windows work in terms of memory management in node-webkit, you may be able to look at the source code and immediately see the problem, I have not been able to figure it out yet though.

At first, I thought that the issue occurred during slow loading of the nw-desktop-notifications.html file (which I serve up on a remote server). However, I created an intentionally slow loading http server to test this and could not reproduce the error in that context either.

Not sure if its helpful, but each of the crash logs looks almost identical with the crashed thread breaking with the same stack trace.

Thanks for your help,
Rob

akry...@gmail.com

unread,
Feb 3, 2013, 11:59:48 AM2/3/13
to node-...@googlegroups.com
Guys,

I can confirm that I've been having the same issue - crashes running macbook air, but also on a different linux machine.  Thanks to your suggestion I've tried removing the following javascript:

window.webkitNotifications.requestPermission()

and everything works fine.  so yeah - definitely some issue with webkitNotifications causing crashes.

Rob Righter

unread,
Feb 4, 2013, 10:23:33 AM2/4/13
to node-...@googlegroups.com, akry...@gmail.com
akry,
Do you have a js example that consistently causes this crash? If so could you post that along with the crash report? That would be super helpful.

Thanks,
Rob

akry...@gmail.com

unread,
Feb 4, 2013, 11:55:40 AM2/4/13
to node-...@googlegroups.com, akry...@gmail.com
sorry i dont have a full example available as its part of the app, but this is the line that caused the crash for me:

window.webkitNotifications.requestPermission()

on os x 10.7 and on linux (havent tried windows but presume its the same) on all the recent versions of node-webkit i've tried

Rob Righter

unread,
Feb 12, 2013, 2:01:47 PM2/12/13
to node-...@googlegroups.com, akry...@gmail.com
You can check to see if window.webkitNotifications are supported before you try to request permission. you can do this by:
if(window.webkitNotifications){}

This will avoid the crash you are seeing.

However, the crash I am experiencing only happens on Mac OSX 10.7.5 and is unrelated to window.webkitNotifications. It happens very rarely (like once a week if you are running the app for hours each day).
Reply all
Reply to author
Forward
0 new messages