On a random basis NR crashes with an error caused by a debug node (I suppose). Attachedd the error that my system log registerd and that cause NR to restart Jun 4 14:31:55 raspberrypi Node-RED[345]: 4 Jun 14:31:55 - [warn] [debug:Errori rilevati sul flow CAMPIONAMENTO SENSORI] Message exceeded m…

[image] zenofmud: Can you upgrade? (I would suggest backing up your SD card before doing the upgrade.) As per this post https://discourse.nodered.org/t/mqtt-node-not-working-after-nr-update/22138 some time ago I tried to update my NR installation but after updating I had an error with the M…

Looking at the other post it looks like you are using docker, is that still true? If so, that is something you should mention right off the bat, even putting it in the topic. Unfortunately, not having ever used docker, I'm not going to be of much help.

No. I'm using a classic installation on Raspberry. The reference to a NR running on docker was only a test in order to check the correct functionality of my current MQTT Broker.

Ok, in that case change the catch node to only catch errors from the mqtt node to see if that is where the problem is coming from.

The problem causing the "RangeError: Maximum call stack size exceeded" is not related to the MQTT client. The MQTT client works correctly wiyh my current setup (NR v 0.20.07) and the MQTT in and out nodes are outside the TAB where the catch node (getting the errors and so causing NR to restart) is p…

So what are the other nodes on that tab? Can you provide the flow?

One of the nodes appears to be flooding the system with errors that overwhelm the catch node. You cannot be sure that it is not the mqtt node. As far as I can see the solution is to limit which nodes the catch node is configured to catch, and home in on which one it is. I would start by checking …

Sorry Colin but I didn't get your point. The catch node that throws me the error and restart NR is "within" the TAB "x". In the TAB "x" there is not any MQTT node....How is it possible that the catch node in the TAB "x" catches errors coming from another TAB (i.e TAB "y"). As far as I know is not p…

[image] zenofmud: So what are the other nodes on that tab? Can you provide the flow? It's a quite complex TAB with tons on nodes. Anyway I've logged on a file all the errors catched by the "catch" node of the TAB in order to understand which node/s generates the errors that flood the debug no…

[image] lenny1972: So why do you presume that one ore more MQTT nodes (that are in TAB "y") may causing this error? I didn't realise there aren't any on that tab. If there aren't any then obviously it isn't one of them :slight_smile: I don't think you had previously mentioned that. [ima…

Debug node causing RangeError: Maximum call stack size exceeded

General

ristomatti 6 June 2020 14:45 24

It's difficult to say anything without knowing how you have set the logging up / without seeing your flow. Could you export and share it? Read this first if you haven't yet:

Topic		Replies	Views
Random crashes with "Maximum call stack size exceeded" General	18	6995	7 September 2019
Node-Red crashes with RangeError: Maximum call stack size exceeded General	26	4493	14 May 2020
Node Red stopped - Max call stack size exceeded General	20	1703	12 October 2019
Hmmm, Node-RED grinds to a halt and is restarting. Any Ideas? General	48	219	29 May 2026
RangeError: Maximum call stack size exceeded General	13	342	27 October 2023

Debug node causing RangeError: Maximum call stack size exceeded

Related topics