# Debug Node / Window: No Show - Solved

**URL:** <https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348>\
**Category:** General\
**Created:** [5 October 2019 11:16 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348 "2019-10-05T11:16:23Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [5 October 2019 11:16 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/1 "2019-10-05T11:16:23Z")

</div>

Upgraded to Node-Red v1.0.0

Now, I cannot see the output from the "Debug" node in the Debug Message Window.

Is there a new setting somewhere?

Alan

 ![37%20AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/e/eb3d12a08963ebf243cded3354325b08c5ce2337.png)

---

<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:** [5 October 2019 12:03 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/2 "2019-10-05T12:03:40Z")

</div>

Have you tried resetting the cache in your browser?

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [5 October 2019 15:39 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/3 "2019-10-05T15:39:49Z")

</div>

Thanks ukmoose. Reset the Browser (Chrome) Cache. Problem solved.

Alan

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [5 October 2019 22:02 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/4 "2019-10-05T22:02:34Z")

</div>

The problem with the Debug Window re-appeared, but with a different twist. This time, it was VERY slow...like not showing up until several seconds after injecting an input.

At the same time, I notice that my computer was working very hard....Chrome was at the top of the list for resource usage.

I had added a chart to the dashboard earlier in the day, so by chance, I removed the chart and immediately noted the debug window working again and responsive and the CPU resources used by Chrome much less.

So....perhaps a new problem.....why is my chart using so much of the CPU and slowing other process down?

Alan

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 October 2019 00:07 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/5 "2019-10-06T00:07:24Z")

</div>

> [@n61ab](#):
>
> .why is my chart using so much of the CPU and slowing other process down?

How many data points was it trying to handle?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [6 October 2019 01:11 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/6 "2019-10-06T01:11:36Z")

</div>

Not only how many data points, but also, how often are `msg`s being sent to the chart?

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [6 October 2019 01:39 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/7 "2019-10-06T01:39:02Z")

</div>

One datapoint, one chart every 5 seconds. Also on same Browser, five other data points to text every 5 seconds.

Alan.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 October 2019 09:56 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/8 "2019-10-06T09:56:55Z")

</div>

Sorry, we meant how many points in total are you allowing onto the chart? 500, 1000?

---

<div class="post-metadata">

**Author:** ![n61ab](https://avatars.discourse-cdn.com/v4/letter/n/cc9497/32.png) [@n61ab](https://discourse.nodered.org/u/n61ab)\
**Post date:** [6 October 2019 11:32 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/9 "2019-10-06T11:32:00Z")

</div>

I reduced the rate to one data point every 60 seconds. That seem to help, but Chrome remains the top user of resources.

 ![Resources](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/7/732a6f69564493ca3b0bb47521ce672542aa04b3.png)

Here is the Chart Configuration:

 ![Chart%20Config](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/3/30e49fba118317c72c1f76d89f9f440169d1cdf4.png)

Here is the Dashboard:

 ![Dashboard](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/48d1eddddb844fe2a12169a6b7a6533451999f5c.png)

Does Chrome resource usage look as expected? Are there any other chart nodes that are more browser resource-efficient?

Alan

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 October 2019 12:02 UTC](https://discourse.nodered.org/t/debug-node-window-no-show-solved/16348/10 "2019-10-06T12:02:51Z")

</div>

Well you appear to be keeping 24hrs of chart with a point every 5 seconds which amounts to 17,280‬ by my reckoning. That is a lot of data for Angular to manage in the browser and a known issue for that chart type.

If you think about how many pixels will be used to display the body of the chart, then divide your 24_60_60 seconds by the number of pixels, you should get a rough figure for the maximum rate at which it is worth sending data.

I don't use Chrome any more but I currently have 24 windows open (each with many tabs) in Microsoft Edge Dev (Chromium based) including 2 complex dashboards (not Dashboard) - 1 using uibuilder/Vue/bootstrap with an embedded Grafana iframe and Grafana itself both with a number of complex charts on them and updating once per minute - and I'm showing between 2.5% and 14% CPU on my i7/16GB RAM Surface Book 2. That depends which tabs are active.