DWC becomes sluggish after a few days
-
I've been noticing that DWC becomes very slow to respond if the page is not reloaded for a few days. This is especially problematic when using an SBC with a display plugged in, since it is not easy to reload the page without a keyboard attached (like in the case of a kiosk mode browser using a touch interface), though it also happens on Windows 10 in Firefox. We are using DWC 2.4.6
She/Her
I work at a local 3D printing shop.
Printers: Micron+ w/Duet 3 Mini, in-progress adaptation of the Jubilee REL onto an E3D MS, Prusa i3 MK3S. -
@curieos, I have had this issue for a long time. I brought it up some time ago but it was not resolved (don't recall exactly why). I eventually figured it was either just me, the browser I was using (Firefox running on Ubuntu) or the fact that I have two DWC's open on two different computers all the time.
It can get to the point where it might take a full second before a character typed in on the browser is echoed back to the browser. This happens on different Duet boards (Duet2Wifi and Duet3 6HC) and has been happening for many versions of DWC and RRF.
When the delay gets too annoying, I close the browser window, open a new browser window and response becomes immediate again. It is extremely annoying but seeing that closing the window and re-opening the window fixes the issue, I am not sure this is an issue with DWC.I will be watching this thread very carefully!
-
@jens55 @curieos I have noticed something similar in Chromium on Raspberry pi, but not in chrome on Windows so assumed it was just the pi running out of RAM. I regularly have DWC open in multiple instances for multiple Duets on my PC for days/weeks on end.
Potentially @chrishamm can provide a pointer on how to provide him with some state dump or information to workout whats happening.
-
@T3P3Tony I'd be happy to provide whatever diagnostic data he could desire. It will have to wait until Monday, though that's a benefit in this case, as the web interface will be quite sluggish then.
-
i have noticed that the wifi connection seems to need a manual refresh now and again as DWC seems to have frozen. reported this a few weeks ago , although not seen this in the latest Duet Web Control 3.5.0-rc.1 release yet
-
@moth4017 That's great if it's fixed in 3.5, but this machine can't be on prerelease firmware.
-
undefined Phaedrux marked this topic as a question
-
@curieos Can confirm it's not fixed in 3.5 running chrome on windows 10
-
@p8blr im running Chrome Version 117.0.5938.132 (Official Build) (64-bit)
still not had any issues -
It happened today for the first time using v3.5 , DWC wasn't updating values had to reload page in chrome.
-
I was seeing something similar not sure if it's related or will even help. By chance I loaded RealVNC to update system and saw the browser instance running on the pi had been caching everything since I hooked up the system and was running slow to the point where everything was just lagging, I never shut the pi down. I closed out the browser in RealVNC and haven't had an issue on the computer browser since. I assume the browser is started automatically when the pi is started and won't be much of an issue if the pi is rebooted every so often.
-
@chrishamm please confirm what information you need to help diagnose this issue.
-
@curieos @jens55 @p8blr I have a suspicion why this is ocurring, and I may have a fix in v3.6 that I could backport to 3.4/3.5. Can you confirm that you are running your boards in standalone mode? Checking the memory usage before and after the issue occurs might be worthwhile, too.
Duet software engineer
-
@chrishamm, thanks for looking into this!
I can confirm that I am running standalone. I will try and get memory used figures when I next see the issue.
I am assuming you are talking memory of the Duet? Just to make sure we are talking about the same thing here - I do not do anything on the Duet side to 'fix' things ... I just close the browser window and start a new instance.Here are M122 results before closing the browser window and after re-opening the browser window on a Duet 6HC and a Duet wifi 2. Both boards seemed a bit sluggish in response but neither was REALLY bad ....duet slow-down tests.txt
I hope this is what you wanted ..... -
@chrishamm In my instance, this machine is running in SBC mode. It's mainly a problem for us since we have a touchscreen hooked up to the pi displaying the web interface, and it's difficult to refresh that browser window without hooking up a keyboard. I notice on my windows computer running Firefox that the interface also becomes sluggish there if I don't refresh the page after a couple days.
In the instance of my computer, only that tab becomes slow to respond. I put my computer to sleep at the end of the day and wake it up when I get in. The instance of DWC has to reconnect when I switch back to that tab.
edit: I can run the Firefox process profiler on that tab if that would be helpful. Right now it's a little slow, I can profile it now and later when it becomes worse. Let me know how I should give it to you.
-
@chrishamm Right now, with Firefox 118 on Windows 10, DWC on DSF is using 1gb of RAM and 100% CPU usage according to Firefox's process manager. I'm not sure what 100% CPU means, maybe 100% of a thread? I profiled it, let me know if you want it/how to get it to you.
She/Her
I work at a local 3D printing shop.
Printers: Micron+ w/Duet 3 Mini, in-progress adaptation of the Jubilee REL onto an E3D MS, Prusa i3 MK3S. -
@curieos will do when I'm back from Formnext. If you could provide that dump it may be useful.
-
@curieos Please send me an email with a link to your dump (e.g. Google Drive or Dropbox) to christian@duet3d.com and I'll have a look at it.
