Node crashing often on my MacBook, but I don't know what is using node - node.js

How do I troubleshoot this? The crashed process pop-up appears every now and then.
It looks like it's a process that immediately crashes, so doesn't appear in the process list.
Process: node [8824]
Path: /usr/local/Cellar/node/10.10.0/bin/node
Identifier: node
Version: ???
Code Type: X86-64 (Native)
Parent Process: plugin_host [8802]
Responsible: node [8824]
User ID: 501
Date/Time: 2019-04-24 15:28:55.712 +0200
OS Version: Mac OS X 10.14.4
Report Version: 12
Bridge OS Version: 3.0
Time Awake Since Boot: 33000 seconds
Time Since Wake: 10000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.62.dylib
Referenced from: /usr/local/bin/node
Reason: image not found
Binary Images:
0x100000000 - 0x100fb808f +node (???) <C0E2FA16-9C1B-3805-9967-EB7543CD9520> /usr/local/bin/node
0x10dbad000 - 0x10dc176ef dyld (655.1.1) <F217F7F8-A795-3109-B77F-B1E2277F3E3B> /usr/lib/dyld

Related

Eclipse 4.4 quit unexpectedly on MacOS - works when run from terminal

I'm using a 2017 MacBook Pro with macOS Mojave version 10.14.3. I'm trying to install Eclipse 4.4 in order to use the GGTS plugin.
I downloaded the installation file from eclipse home page and unzipped it to a folder named "eclipse", by default.
I moved Eclipse.app to the Applications folder, but when I start the program, it showed an error dialog saying Eclipse quit unexpectedly.
However, when I run eclipse from the terminal, it worked out just fine, so I'm confused what's the underlying problem with this.
Here's the log
Process: eclipse [1381]
Path: /Applications/Eclipse.app/Contents/MacOS/eclipse
Identifier: org.eclipse.platform.ide
Version: 4.4.0 (4.4.0.I20140606-1215)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: eclipse [1381]
User ID: 501
Date/Time: 2019-02-01 15:25:06.911 -0700
OS Version: Mac OS X 10.14.3 (18D42)
Report Version: 12
Bridge OS Version: 3.0 (14Y674)
Anonymous UUID: 982D7B17-3CD6-65E7-C0E9-80F38A781B0B
Sleep/Wake UUID: AFBA951A-5AAC-4A65-A546-79D101B90607
Time Awake Since Boot: 2600 seconds
Time Since Wake: 1000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000034
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1381]
VM Regions Near 0x34:
-->
__TEXT 0000000100000000-0000000100004000 [ 16K] r-x/rwx SM=COW /Applications/Eclipse.app/Contents/MacOS/eclipse
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x00007fff4b48c11b CFBundleGetFunctionPointerForName + 13
1 org.eclipse.platform.ide 0x000000010000306b findSymbol + 66
2 org.eclipse.platform.ide 0x00000001000017f6 original_main + 1572
3 org.eclipse.platform.ide 0x0000000100001eb5 main + 1230
4 org.eclipse.platform.ide 0x0000000100001090 start + 52
Thread 1:
0 libsystem_pthread.dylib 0x00007fff788a53f8 start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796
Thread 2:
0 libsystem_pthread.dylib 0x00007fff788a53f8 start_wqthread + 0
1 ??? 0x0000000000001703 0 + 5891
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00006000002002c0 rbx: 0x0000000000000000 rcx: 0x6974696e49746573 rdx: 0x0000000000000006
rdi: 0x0000000000000000 rsi: 0x00006000002002c0 rbp: 0x00007ffeefbff970 rsp: 0x00007ffeefbff960
r8: 0x736772416c616974 r9: 0x0000000000000000 r10: 0x00007ffeefbff7f0 r11: 0x00007fff4b48c10e
r12: 0x00000001000043f8 r13: 0x0000600002608060 r14: 0x00006000002002c0 r15: 0x0000600000c04090
rip: 0x00007fff4b48c11b rfl: 0x0000000000010206 cr2: 0x00007fffa412ec88
Logical CPU: 0
Error Code: 0x02000170
Trap Number: 133
I've been searching for solutions everywhere but haven't found any. If you neeed more information about the error, or have any suggestion, please let me know. This is getting rather frustrating for me.
Thanks in advance!
This is due to an incorrect installation (see Eclipse bug 390071).
Eclipse 4.4 (Luna) was not a proper macOS application. You must move the complete Eclipse directory to /Applications rather than just Eclipse.app
Starting from Eclipse 4.5 (Mars) Eclipse is packaged as a proper app.

Unable to start STS3 Eclipse under macOS High Sierra

I am unable to start the STS3 Eclipse IDE. I am using macOS High Sierra Version 10.13.6. and STS version 3.9.6.201809180749-RELEASE-e49. The startup fails with SIGSEV.
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
Full error trace can be seen here:
https://pastebin.com/5gQ9e1Jt
It looks like the STS process crashes when looking up the JVM or starting the JVM (just a wild guess here). I would try to solve this my downloading a recent JDK 1.8 from Oracle and specify that JVM in the STS.ini file, like you would do in the eclipse.ini for a regular Eclipse installation (as described here: https://wiki.eclipse.org/Eclipse.ini).

After Upgrading to macOS High Sierra (version 10.13.1), Eclipse Neon 1a crashes on builds

Eclipse neon 1a (release 4.6.1). Has anyone else been experiencing this issue? I attempt to "build all" via "command b" and every other time I execute the command Eclipse crashes.
Process: eclipse [24118]
Path:
/private/var/folders/*/Eclipse.app/Contents/MacOS/eclipse
Identifier: org.eclipse.platform.ide
Version: 4.6.1 (4.6.1.M20160907-1200)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: eclipse [24118]
User ID: 501
Date/Time: 2017-11-15 13:12:14.819 -0800
OS Version: Mac OS X 10.13.1 (17B48)
Report Version: 12
Anonymous UUID: 9FBBDD4C-868D-C2C6-D335-3056CD6A5E11
Sleep/Wake UUID: D8ABAD67-BD34-4AFA-AE70-BCE2463C3A2F
Time Awake Since Boot: 180000 seconds
System Integrity Protection: enabled
Notes: Translocated Process
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000138b3f2f0
Exception Note: EXC_CORPSE_NOTIFY

ntdll.dll is crashing IIS App Pool with 0xc0000008

I have an IIS Web App that has been consistently crashing every day after encountering a series of 0xc000008 exceptions. The error stops getting logged in event viewer after occurring 5 times, however I'm confident it stops after 5 occurrences because the IIS App Pool's Rapid-Fail Protection is configured to kick in after 5 exceptions. I am further convinced the Rapid-Fail Protection is kicking in because I have had to manually recycle/restart the App Pool everyday.
I installed DebugDiag to help trace the exceptions seen in Event Viewer but it has been just as vague as the errors in Event Viewer. At this point I have reached the edge of my very limited knowledge with IIS and ASP.NET and unfortunately haven't been able to try much because I can't get a sensible error message. I've included the error messages from each source below. Any help in understanding them or knowing where to go from here would be greatly appreciated it.
This is a MVC3 Web App written in C# using .NET Framework 4.5.2 running on Windows Server 2012 R2. All applicable windows updates have been installed.
I've enable Failed Request Tracing to hopefully get some more insight into the error.
Event Viewer Error
Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: ntdll.dll, version: 6.3.9600.16502, time stamp: 0x52c359e8
Exception code: 0xc0000374
Fault offset: 0x00000000000f387c
Faulting process id: 0x1588
Faulting application start time: 0x01d239d9a9246e12
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 6dd5b05a-a5ce-11e6-80c5-005056bf6041
Faulting package full name:
Faulting package-relative application ID:
Error Analysis from DebugDiag
Report for w3wp__dataximg__PID__2168__Date__11_01_2016__Time_01_03_36PM__593__Second_Chance_Exception_C0000008.dmp
Type of Analysis Performed Combined Crash/Hang Analysis
Machine Name localhost
Operating System Windows Server 2012
Number Of Processors 2
Process ID 2168
Process Image c:\Windows\System32\inetsrv\w3wp.exe
Command Line c:\windows\system32\inetsrv\w3wp.exe -ap "dataximg" -v "v2.0" -l "webengine4.dll" -a \\.\pipe\iisipm21b77437-5c32-41dc-958b-556a03f34971 -h "C:\inetpub\temp\apppools\dataximg\dataximg.config" -w "" -m 0 -t 20 -ta 0
System Up-Time 35 day(s) 23:08:46
Process Up-Time 00:00:07
Processor Type X64
Process Bitness 64-Bit
Top 5 Threads by CPU time
Note - Times include both user mode and kernel mode for each thread
Thread ID: 0 Total CPU Time: 00:00:00.030 Entry Point for Thread: w3wp!wmainCRTStartup
Thread ID: 2 Total CPU Time: 00:00:00.015 Entry Point for Thread: ntdll!TppWorkerThread
Thread ID: 1 Total CPU Time: 00:00:00.000 Entry Point for Thread: nativerd!NOTIFICATION_THREAD::ThreadProc
Thread ID: 3 Total CPU Time: 00:00:00.000 Entry Point for Thread: ntdll!TppWorkerThread
Thread ID: 4 Total CPU Time: 00:00:00.000 Entry Point for Thread: w3tp!THREAD_MANAGER::ThreadManagerThread
Exception Information
In w3wp__appimg__PID__2168__Date__11_01_2016__Time_01_03_36PM__593__Second_Chance_Exception_C0000008.dmp the assembly instruction at ntdll!KiRaiseUserExceptionDispatcher+3a in C:\Windows\System32\ntdll.dll from Microsoft Corporation has caused an unknown exception (0xc0000008) on thread 1
Module Information
Image Name: C:\Windows\System32\ntdll.dll Symbol Type: PDB
Base address: 0x00000003`00905a4d Time Stamp: Tue Dec 31 18:57:28 2013
Checksum: 0x00000000`00000000 Comments:
COM DLL: False Company Name: Microsoft Corporation
ISAPIExtension: False File Description: NT Layer DLL
ISAPIFilter: False File Version: 6.3.9600.16502 (winblue_gdr.131231-1531)
Managed DLL: False Internal Name: ntdll.dll
VB DLL: False Legal Copyright:© Microsoft Corporation. All rights reserved.
Loaded Image Name: ntdll.dll Legal Trademarks:
Mapped Image Name: Original filename: ntdll.dll
Module name: ntdll Private Build:
Single Threaded: False Product Name: Microsoft® Windows® Operating System
Module Size: 1.66 MBytes Product Version: 6.3.9600.16502
Symbol File Name: c:\symbols\ntdll.pdb\A525CD5C71214238B761A6EFA0B3402D1\ntdll.pdb Special Build: &

Why does ADT let's me export once. 2nd Export it crashes OSX 10.6

I have a weird problem since a few days. After exporting a project for android once it works fine the 2nd export I do eclipse crashes with this error:
Identifier: org.eclipse.eclipse
Version: 3.8 (3.8)
Code Type: X86-64 (Native)
Parent Process: launchd [269]
Date/Time: 2013-03-12 21:36:13.365 +0100
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 321292 sec
Crashes Since Last Report: 3
Per-App Interval Since Last Report: 44806 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: 52A136CA-CDAE-4661-B166-51B04A18C21C
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x000000011f1c965f
Crashed Thread: 46 Java: ModalContext
Any clues. Running: adt-bundle-mac-x86_64-20130219
SIGBUS looks like bad RAM but then other things would act up aswell?
B
I guess that's random. As mentioned in this thread it looks like it can happen if eclipse is building your project at the same time as you're exporting it. You could try to disable the "build automatically" option in eclipse while you're exporting it.

Resources