How to get node id from syslog on crash

Hi All,

I'd like to identify the node where my app crashes but I cannot really identify anything that could be used as a node id I could search for in the editor.

Does anyone have any hint how to find the node responsible for the crash?

Here is a syslog excerpt from a crash:

Apr 5 19:32:16 raspberrypi Node-RED[11264]: <--- Last few GCs --->
Apr 5 19:32:16 raspberrypi Node-RED[11264]: [11264:0x248ec88] 128390132 ms: Mark-sweep 250.2 (256.8) -> 249.8 (256.8) MB, 1186.4 / 0.5 ms (average mu = 0.130, current mu = 0.012) allocation failure scavenge might not succeed
Apr 5 19:32:16 raspberrypi Node-RED[11264]: [11264:0x248ec88] 128391552 ms: Mark-sweep 250.3 (256.8) -> 249.8 (256.8) MB, 1402.8 / 0.3 ms (average mu = 0.071, current mu = 0.012) allocation failure scavenge might not succeed
Apr 5 19:32:16 raspberrypi Node-RED[11264]: <--- JS stacktrace --->
Apr 5 19:32:16 raspberrypi Node-RED[11264]: ==== JS stack trace =========================================
Apr 5 19:32:16 raspberrypi Node-RED[11264]: 0: ExitFrame [pc: 0xe50420]
Apr 5 19:32:16 raspberrypi Node-RED[11264]: Security context: 0x3f30e225
Apr 5 19:32:16 raspberrypi Node-RED[11264]: 1: baseClone [0x2f35b865] [/usr/local/lib/node_modules/node-red/node_modules/lodash.clonedeep/index.js:~841] [pc=0x6d5c32f0](this=0x470411c9 ,3106411,0x5bbc0355 ,0x5bbc0355 ,0x5bbc0275 ,0x3f313445 <String[#2]: id>,0x6cf63471 ,0x28432475 )
Apr 5 19:32:16 raspberrypi Node-RED[11264]: 2: /* anonymous */ [0x56b4b1a9] [/...
Apr 5 19:32:16 raspberrypi Node-RED[11264]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Apr 5 19:32:17 raspberrypi Node-RED[11264]: Writing Node.js report to file: report.20210405.193216.11264.0.001.json
Apr 5 19:32:17 raspberrypi Node-RED[11264]: Node.js report completed
Apr 5 19:32:17 raspberrypi systemd[1]: nodered.service: Main process exited, code=killed, status=6/ABRT

Thanks&regards,
r0ller

I would say that you could already guess the problem. Node has run out of stack space and the most likely culprit is Lodash's deep object clone function.

Because this is an unhandled exception deep inside Node.js, Node-RED has no way of reporting the node that "caused" the issue even if it was able to know which it probably couldn't since an out of memory exception may not always happen in the place that has used up most of the memory.

Yepp, that I could figure out myself :slight_smile: Thanks anyway!