Upgrade to 3.3. of IDE causes "nwjs Helper EH quit unexpectedly."

I upgraded to 3.3 and now on starting the VIPER IDE I get “nwjs Helper EH quit unexpectedly” and it doesn’t see the board… 

Has anyone else seen this problem?


mmm…strange, I can’t reproduce it…

Can you click Report, and paste a more detailed crash description?

Process: nwjs Helper EH [1237] Path: /Users/USER/Documents/*/nwjs.app/Contents/Frameworks/nwjs Helper EH.app/Contents/MacOS/nwjs Helper EH Identifier: nwjs Helper EH Version: 41.0.2272.76 (2272.76) Code Type: X86-64 (Native) Parent Process: nwjs [1231] Responsible: nwjs Helper EH [1237] User ID: 502 Date/Time: 2016-01-26 15:35:36.899 +0000 OS Version: Mac OS X 10.11.3 (15D21) Report Version: 11 Anonymous UUID: DDFFC0A4-7075-5A6E-578F-CE672562E1EB Sleep/Wake UUID: 84CE86EB-130E-4B96-81CF-3CA773D4DA63 Time Awake Since Boot: 160000 seconds System Integrity Protection: enabled Crashed Thread: 0 CrUtilityMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0: --> __TEXT 0000000104039000-000000010403a000 [ 4K] r-x/rwx SM=COW /Users/USER/Documents/*/nwjs.app/Contents/Frameworks/nwjs Helper EH.app/Contents/MacOS/nwjs Helper EH Thread 0 Crashed:: CrUtilityMain Dispatch queue: com.apple.main-thread 0 nwjs Framework 0x0000000104670d0e v8::internal::Isolate::Exit() + 14 1 nwjs Framework 0x000000010636cdcf 0x10403c000 + 36900303 2 nwjs Framework 0x0000000105ad78ca 0x10403c000 + 27900106 3 nwjs Framework 0x0000000106af57a3 0x10403c000 + 44799907 4 nwjs Framework 0x0000000106f0fff9 0x10403c000 + 49102841 5 nwjs Framework 0x0000000106effc24 0x10403c000 + 49036324 6 nwjs Framework 0x0000000106eff176 0x10403c000 + 49033590 7 nwjs Framework 0x000000010408e812 ContentMain + 66 8 io.nwjs.nw.helper.EH 0x0000000104039f24 0x104039000 + 3876 Thread 1: 0 libsystem_kernel.dylib 0x00007fff9853d6de __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8f4d1729 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff8f4cf365 start_wqthread + 13 Thread 2:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff9853dff6 kevent_qos + 10 1 libdispatch.dylib 0x00007fff9e2da099 _dispatch_mgr_invoke + 216 2 libdispatch.dylib 0x00007fff9e2d9d01 _dispatch_mgr_thread + 52 Thread 3: 0 libsystem_kernel.dylib 0x00007fff9853d6de __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8f4d1729 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff8f4cf365 start_wqthread + 13 Thread 4: 0 libsystem_kernel.dylib 0x00007fff9853d6de __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff8f4d1729 _pthread_wqthread + 1283 2 libsystem_pthread.dylib 0x00007fff8f4cf365 start_wqthread + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fff98537386 mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff985367c7 mach_msg + 55 2 nwjs Framework 0x00000001070eb885 0x10403c000 + 51050629 3 libsystem_pthread.dylib 0x00007fff8f4d1c13 _pthread_body + 131 4 libsystem_pthread.dylib 0x00007fff8f4d1b90 _pthread_start + 168 5 libsystem_pthread.dylib 0x00007fff8f4cf375 thread_start + 13 Thread 6:: Chrome_ChildIOThread 0 libsystem_kernel.dylib 0x00007fff9853dfc6 kevent + 10 1 nwjs Framework 0x0000000104879613 0x10403c000 + 8640019 2 nwjs Framework 0x000000010487709d 0x10403c000 + 8630429 3 nwjs Framework 0x0000000104101bc0 0x10403c000 + 809920 4 nwjs Framework 0x0000000104154983 0x10403c000 + 1149315 5 nwjs Framework 0x000000010414154d 0x10403c000 + 1070413 6 nwjs Framework 0x000000010416cb03 0x10403c000 + 1248003 7 nwjs Framework 0x0000000104168cfb 0x10403c000 + 1232123 8 libsystem_pthread.dylib 0x00007fff8f4d1c13 _pthread_body + 131 9 libsystem_pthread.dylib 0x00007fff8f4d1b90 _pthread_start + 168 10 libsystem_pthread.dylib 0x00007fff8f4cf375 thread_start + 13 Thread 7:: OptimizingCompi 0 libsystem_kernel.dylib 0x00007fff985373c2 semaphore_wait_trap + 10 1 nwjs Framework 0x0000000104852267 0x10403c000 + 8479335 2 nwjs Framework 0x00000001046f70b5 v8::internal::OptimizingCompilerThread::Run() + 101 3 nwjs Framework 0x0000000104853837 0x10403c000 + 8484919 4 libsystem_pthread.dylib 0x00007fff8f4d1c13 _pthread_body + 131 5 libsystem_pthread.dylib 0x00007fff8f4d1b90 _pthread_start + 168 6 libsystem_pthread.dylib 0x00007fff8f4cf375 thread_start + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x00007f8e29513aa0 rcx: 0x0000000000000117 rdx: 0x00007fff7a54d000 rdi: 0x00007f8e2a00ba00 rsi: 0x0000000000000000 rbp: 0x00007fff5bbc6740 rsp: 0x00007fff5bbc6730 r8: 0x0000000000000000 r9: 0x00007f8e29406990 r10: 0x00000000a2a119ff r11: 0x00007f8e29400000 r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x00007fff5bbc67e0 r15: 0x00007fff5bbc67d0 rip: 0x0000000104670d0e rfl: 0x0000000000010206 cr2: 0x0000000000000000 Logical CPU: 0 Error Code: 0x00000004 Trap Number: 14 Binary Images: 0x104039000 - 0x104039fff +io.nwjs.nw.helper.EH (41.0.2272.76 - 2272.76) <09DC9F8E-3B87-3D7A-B8EB-6BCB98062210> /Users/USER/Documents/*/nwjs.app/Contents/Frameworks/nwjs Helper EH.app/Contents/MacOS/nwjs Helper EH 0x10403c000 - 0x1080f9fbf +nwjs Framework (0) /Users/USER/Documents/*/nwjs.app/Contents/Frameworks/nwjs Framework.framework/nwjs Framework 0x108773000 - 0x1087aafff com.apple.audio.midi.CoreMIDI (1.10 - 88) <4A755EA1-3CF5-32A6-8939-8D2998577406> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI

External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 1 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 111473 thread_create: 0 thread_set_state: 0

```

I had to cut the report to enable pasting… Let me know if there is anything missing… It happened every time. Clearly I can’t access the board

I deinstalled viper and node.js and reinstalled viper to see if it made any difference… No change. Currently Viper is unusable. Any ideas?

Thanks for the report.

That’s weird, I can’t reproduce it in El Capitan nor in Yosemite…and I can’t find anything about nw.js crashing in CrUtilityMain…

Do you have any program blocking outgoing connections (like Little Snitch or some other firewall)? Can you try starting Viper without being connected to the internet (wifi and ethernet off)?


You can also try the following and check if it solve the issue:

  • download nw.js version 0.13 beta 4 from here https://github.com/nwjs/nw.js
  • go to Documents/Viper/env/sys/browser
  • substitute the nwjs app you find there with the 0.13 version
Let me know, if nothing works I’ll report the issue to nw.js community

Tried… I could get the 0.13 beta build to start standalone… but I couldn’t get it to run as the Viper IDE (nothing happened). 

I’ve deinstalled Viper numerous times now and I can’t get any further… It all worked fine until the 3.3 upgrade… Is there anyway I could try and get hold of the 3.2 build or would that try and upgrade itself to the latest version on install?

I prepared a snapshot of the r0.3.2 IDE. From here you can download the ide package
Then you have to remove r0.3.3 and put r0.3.2 in its place:

  • Remove or rename Documents/Viper/env/core/official/ide
  • uncompress the archive to a folder
  • copy the contents under Documents/Viper/env/core/official/ide
  • start viper  (with the 0.12 version of nw.js)
If it works, at least we have a starting point, and a rapid diff of the IDE code should point us to the culprit.


Sorry it took me a while to get to this… I build most of the project on a raspberry and now I’m going to try and back port it to the photon…

Ok… Good news… Not sure how I got there but I downgraded the IDE to 3.2 with your code… Whilst it crashed on the first restart… The second didn’t. Taking a chance I updated everything to the latest versions and it all started… Everything appears to be working. Thanks for helping me through this…