DWC becomes sluggish after a few days

p8blr

@curieos Can confirm it's not fixed in 3.5 running chrome on windows 10

moth4017

@p8blr im running Chrome Version 117.0.5938.132 (Official Build) (64-bit)
still not had any issues

moth4017

It happened today for the first time using v3.5 , DWC wasn't updating values had to reload page in chrome.

edsped

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.

T3P3Tony

@chrishamm please confirm what information you need to help diagnose this issue.

chrishamm

@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.

jens55

@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 .....

curieos

@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.

curieos

@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.

chrishamm

@curieos will do when I'm back from Formnext. If you could provide that dump it may be useful.

chrishamm

@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.