# Node-red crashes

**URL:** https://discourse.nodered.org/t/node-red-crashes/9590
**Category:** General
**Created:** [29 March 2019 20:16 UTC](https://discourse.nodered.org/t/node-red-crashes/9590 "2019-03-29T20:16:48Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![olab](https://avatars.discourse-cdn.com/v4/letter/o/d07c76/32.png) [@olab](https://discourse.nodered.org/u/olab)
#### Post date: [29 March 2019 20:16 UTC](https://discourse.nodered.org/t/node-red-crashes/9590/1 "2019-03-29T20:16:49Z")

</div>

Hello,

I just created a bad flow in my node red-project. Now the node-red refuses to start with the following message:

29 Mar 20:03:38 - [info] Started flows  
29 Mar 20:03:42 - [red] Uncaught Exception:  
29 Mar 20:03:42 - TypeError: "list" argument must be an Array of Buffers  
at Function.Buffer.concat (buffer.js:314:13)  
at completeSend (/usr/lib/node\_modules/node-red/nodes/core/logic/17-split.js:469:40)  
at Timeout. (/usr/lib/node\_modules/node-red/nodes/core/logic/17-split.js:630:29)  
at ontimeout (timers.js:386:11)  
at tryOnTimeout (timers.js:250:5)  
at Timer.listOnTimeout (timers.js:214:5)

Any good idea on how to fix this issue?

O

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [29 March 2019 20:25 UTC](https://discourse.nodered.org/t/node-red-crashes/9590/2 "2019-03-29T20:25:50Z")

</div>

Hi @olab

What version of node-red are you using?

If you are on the latest 0.20 release, you can start Node-RED with the `--safe` command line parameter - this will load your flows but not start them running. You'll then be able to edit them to fix-up the problem.

If you are on 0.19 or earlier, you'll probably have to hand edit your flow file (NR logs the full path to the file on startup to help you find it), look for any Join nodes and either remove them, or temporarily change their ID to break the wires coming into them and stop the flow.

That said, this is an uncaught exception in a core Join node - which really needs to be fixed. Could you raise an issue with as much detail as you can? We'd need to know what your flow is doing with any Join nodes you have - how are they configured? What messages are you passing them etc etc.

---

<div class="post-metadata">

### Author: ![olab](https://avatars.discourse-cdn.com/v4/letter/o/d07c76/32.png) [@olab](https://discourse.nodered.org/u/olab)
#### Post date: [29 March 2019 21:04 UTC](https://discourse.nodered.org/t/node-red-crashes/9590/3 "2019-03-29T21:04:51Z")

</div>

Thank you!

I didn't have the latest release but did an upgrade of node-red and js. Then I was able to start node-red in safe mode and modify my faulty program.

O

---

<div class="post-metadata">

### Author: ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [3 July 2019 13:50 UTC](https://discourse.nodered.org/t/node-red-crashes/9590/5 "2019-07-03T13:50:58Z")

</div>

> [@olab](#):
>
> Then I was able to start node-red in safe mode and modify my faulty program.

Which is what they did over 3 months ago...
