Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RangeError: Maximum call stack size exceeded crashes Node-RED in endless loop at startup.
See original GitHub issueSoftware and Package Versions
| Software | Version |
|---|---|
| Node.JS | 10.15.3 |
| npm | 6.11.2 |
| Node-RED | 0.20.7 |
| uibuilder node | not shown but not latest |
| uibuilderFE | not shown but not latest |
| OS | Raspbian GNU/Linux (stretch) |
| Browser | Chrome Version 76.0.3809.100 (Official Build) (64-bit) |
How is Node-RED installed? Where is uibuilder installed?
Installed with Node-RED admin interface “Manage Palette”.
Not sure if this was fixed in latest uibuilder version. But graceful-fs node-module caused Node-RED to endlessly crash when starting node-red-start and crash as soon as editor endpoint at http://localhost:1880 was reached through browser after using node-red --safe.
Screenshot of startup.
Screenshot with [warn] log after graceful-fs module removed.
I have updated uibuilder to latest and can see graceful-fs installed no issues till now.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Just to note that someone raised a similar issue in the forum. However, that wasn’t related to uibuilder so it looks like this issue is only indirectly related to uibuilder.
The common factor actually seems to be node-red-contrib-npm
https://discourse.nodered.org/t/random-crashes-with-maximum-call-stack-size-exceeded/15099/3
Working fine now.