# Nodes become unresponsive after a while

**URL:** <https://discourse.nodered.org/t/nodes-become-unresponsive-after-a-while/95847>\
**Category:** General\
**Created:** [7 March 2025 09:55 UTC](https://discourse.nodered.org/t/nodes-become-unresponsive-after-a-while/95847 "2025-03-07T09:55:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vie5i](https://avatars.discourse-cdn.com/v4/letter/v/7feea3/32.png) [@vie5i](https://discourse.nodered.org/u/vie5i)\
**Post date:** [7 March 2025 09:55 UTC](https://discourse.nodered.org/t/nodes-become-unresponsive-after-a-while/95847/1 "2025-03-07T09:55:52Z")

</div>

After a few hours of normal operation I've noticed since v4.08 the nodes become unresponsive.  
They do not send messages through.  
I don't see anything wrong.  
I can modify and deploy the software but when I send a command it does not go through which means commands don't get sent through.  
Restarting it does make it responsive again but then after a few hours same issue occurs.  
Please see the screenshot attached.  
I have injected a boolean true but it does not go through to debug.

Regards

 ![2025-03-07_09-42](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/1/e12d3b1bbac505b87202076df4c8e5ac5ff389cd.png)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 March 2025 10:17 UTC](https://discourse.nodered.org/t/nodes-become-unresponsive-after-a-while/95847/2 "2025-03-07T10:17:15Z")

</div>

Welcome to the forum @vie5i

Are you using charts in your dashboard? If so then work out the total number of points stored in your charts when a few hours has elapsed. If you find that is many thousands then that is probably the problem. For example, a chart with four lines with data every second, would be 14000 points per hour, so if you have specified a time span of 4 hours that would be approaching 60,000 data points which have to shuffled down in the browser every second.

If it is not that then run a system monitor on the machine and see if something is hogging up the processor.

---

<div class="post-metadata">

**Author:** ![vie5i](https://avatars.discourse-cdn.com/v4/letter/v/7feea3/32.png) [@vie5i](https://discourse.nodered.org/u/vie5i)\
**Post date:** [7 March 2025 10:45 UTC](https://discourse.nodered.org/t/nodes-become-unresponsive-after-a-while/95847/3 "2025-03-07T10:45:40Z")

</div>

Thank you for the reply.  
I am using charts.  
Points update every 15minutes.  
Node-red was hogging up the CPU.  
I disabled all charts the CPU eased off.  
Hopefully that was causing it.  
Will monitor over the next few days and see the results.

Regards

---

<div class="post-metadata">

**Author:** ![vie5i](https://avatars.discourse-cdn.com/v4/letter/v/7feea3/32.png) [@vie5i](https://discourse.nodered.org/u/vie5i)\
**Post date:** [8 March 2025 20:28 UTC](https://discourse.nodered.org/t/nodes-become-unresponsive-after-a-while/95847/4 "2025-03-08T20:28:20Z")

</div>

Hello,

I found I had created a loop which went unnoticed, this was causing node-red to use high CPU upwards of 90%.  
This would also make the client machine browser to use high CPU.  
It has now stabilized and node-red is using round 5% CPU.  
I hope somebody else finds this useful.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 March 2025 20:29 UTC](https://discourse.nodered.org/t/nodes-become-unresponsive-after-a-while/95847/5 "2025-03-22T20:29:06Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.