JS Stacktrace crash error

[Ben Orchard]

After being rock solid for more than 8 months, Node-RED running on Windows 10 has started crashing on me.
Last node I recall installing and using is the Watson IoT node. May or may not be related.

The problem I have is that the stacktrace is meaningless to me....

Would love some help.....

// snip log with the usual status messages... Everything is running fine. The next three errors are from the USGS flow. Not too worried about them.. Everything from here is straight from the log.

7 May 21:52:34 - [error] [domain-write-ds:8d4dccdc.cefc7] Cannot read property 'time' of undefined

7 May 21:52:34 - [error] [domain-write-ds:aa93d98b.8b8978] Cannot read property 'place' of undefined

7 May 21:52:34 - [error] [domain-write-ds:cbe72d4a.d3f7e] Cannot read property 'mag' of undefined

<--- Last few GCs --->

50813482 ms: Mark-sweep 1240.1 (1435.0) -> 1240.0 (1435.0) MB, 2008.2 / 0.0 ms [allocation failure] [GC in old space requested].

50815374 ms: Mark-sweep 1240.0 (1435.0) -> 1240.0 (1435.0) MB, 1891.8 / 0.0 ms [allocation failure] [GC in old space requested].

50817361 ms: Mark-sweep 1240.0 (1435.0) -> 1248.3 (1404.0) MB, 1986.2 / 0.0 ms [last resort gc].

50819329 ms: Mark-sweep 1248.3 (1404.0) -> 1257.1 (1404.0) MB, 1968.6 / 0.0 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 000003092D9CFB61 <JS Object>

    1: send [C:\Users\ben\AppData\Roaming\npm\node_modules\node-red\node_modules\ws\lib\WebSocket.js:231] [pc=00000308A5FC2F8B]

 (this=000003683E1A00F1 <a WebSocket with map 0000036C44A13879>,data=0000008A431FFFD1 <String[89]: {"topic":"status/6e1a5a2.8db8

7a4","data":{"fill":"green","shape":"dot","text":"reading"}}>,options=000003092D904381 <undefined>,cb=000003092D904381 <undefine

d>)

    2: ...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

C:\Users\ben\.node-red>node-red

8 May 08:16:54 - [info]

Welcome to Node-RED

===================

8 May 08:16:54 - [info] Node-RED version: v0.16.1

8 May 08:16:54 - [info] Node.js  version: v6.9.4

8 May 08:16:54 - [info] Windows_NT 6.1.7601 x64 LE

8 May 08:16:56 - [info] Loading palette nodes

8 May 08:16:59 - [info] Dashboard version 2.3.5 started at /ui

8 May 08:17:02 - [warn] ------------------------------------------------------

8 May 08:17:02 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node

8 May 08:17:02 - [warn] [tail] Not currently supported on Windows.

8 May 08:17:02 - [warn] [mikrotik] Error: mikrotik-device already registered

8 May 08:17:02 - [warn] ------------------------------------------------------

8 May 08:17:02 - [info] Settings file  : \Users\ben\.node-red\settings.js

8 May 08:17:02 - [info] User directory : \Users\ben\.node-red

8 May 08:17:02 - [info] Flows file     : \Users\ben\.node-red\flows_PAC_THINKPAD.json

8 May 08:17:02 - [info] Server now running at http://127.0.0.1:2880/

8 May 08:17:02 - [info] Starting flows

[BaseClient:connect] Connecting to IoTF with host : ssl://domain.messaging.internetofthings.ibmcloud.com:8883

8 May 08:17:02 - [info] Started flows

8 May 08:17:02 - [info] [tcp in:hemet:22] listening on port 22022

8 May 08:17:02 - [info] [tcp in:palmdale:20] listening on port 22020

8 May 08:17:02 - [info] [tcp in:island:22025] listening on port 22025

8 May 08:17:02 - [info] [tcp in:corona:22026] listening on port 22026

// Snip log with a bunch more tcp and udp in listener nodes

8 May 08:17:03 - [info] [mqtt-broker:8779018.d0136] Connected to broker: mqtt://demo.domain.com:1883

[GatewayClient:connect] GatewayClient Connected

(node:58548) Warning: Possible EventEmitter memory leak detected. 11 timeout listeners added. Use emitter.setMaxListeners() to i

ncrease limit

8 May 08:22:05 - [error] [domain-write-ds:8d4dccdc.cefc7] Cannot read property 'time' of undefined

8 May 08:22:05 - [error] [domain-write-ds:aa93d98b.8b8978] Cannot read property 'place' of undefined

8 May 08:22:05 - [error] [domain-write-ds:cbe72d4a.d3f7e] Cannot read property 'mag' of undefined

// Back up and running. Have transposed the word 'domain' in a few sensitive places.

[Dave C-J]

At a glance it looks like out of memory... So I guess it's leaking over time ?

sent from phone

[Ben Orchard]

What node is leaking?

Usually in the crash log you see a name, but in this case, I have no idea whos leaking.

[Nick O'Leary]

You can't tell from that log. You can see what node was trying to allocate some more memory at the time of the crash, but that doesn't mean that node was leaking memory.

Nick

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/109b03bd-eb88-48ff-b6e5-c0d4947adb3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dave C-J]

Well it looks like the garbage collector couldn't allocate memory, and the websocket was trying to do something, but they are just what tipped it over the edge. Not easy to see on my phone, you could try running node-red-pi instead as that starts node red with a smaller member limit so the gc kicks in sooner. But yeah need to track down that node. 

sent from phone