@JohnGalt if you hadn’t erased the logs, the pm2 log MIGHT have had a fault listed…
2.37 is the current release, 6 months newer… electron at 42.5.2
supposedly this could help find cause
Analyze the Crash Dump
Because Electron code is pre-compiled, looking at a raw dump file yields only unreadable memory addresses.
You need to symbolicate the dump using matching Electron debugging symbols.
The CLI Tool (electron-minidump)
The easiest open-source way to inspect a .dmp file locally is using the electron- minidump CLI tool.
It automatically fetches the matching Electron symbols and outputs a readable stack trace.
Install the utility:
sudo npm install -g electron-minidump
Analyze your file:
electron-minidump -f /path/to/your/file.dmp