Page 2 of 2
Re: possible memory leak then 'resources not found'
Posted: Thu Jun 12, 2025 12:21 pm
by wesgeorge
ok, I'll post there as well, because yeah it's definitely still happening, and it's not specific to WUs being paused. I just had to punt it this AM for using 9GB of memory, WU has not been paused, but the system was restarted yesterday due to it being patch tuesday.
Re: possible memory leak then 'resources not found'
Posted: Thu Jun 12, 2025 4:23 pm
by muziqaz
It's ok, we have reproducible scenario, so Dev can work on it
Re: possible memory leak then 'resources not found'
Posted: Fri Jun 13, 2025 1:40 pm
by arisu
I'll run the client under heaptrack for a few days and see if I can glean anything useful from it.
Re: possible memory leak then 'resources not found'
Posted: Fri Jun 13, 2025 7:38 pm
by muziqaz
arisu wrote: ↑Fri Jun 13, 2025 1:40 pm
I'll run the client under heaptrack for a few days and see if I can glean anything useful from it.
Linux does not really suffer from this. Or I have not seen it happen on my Linux boxes. Windows however, easily reproducible: download a WU, run it for a bit, pause it, restart the PC, wait for fahclient to start up (don't start folding), observe it blow up in memory usage
Re: possible memory leak then 'resources not found'
Posted: Sat Jun 14, 2025 10:25 am
by arisu
I've noticed a drastic increase in memory usage on Linux at times, with RSS exceeding 6 GB. A restart of the client fixes it, bringing usage down to about 60 MB.
Re: possible memory leak then 'resources not found'
Posted: Sat Jun 14, 2025 3:08 pm
by Joe_H
Yes, but is that a permanent increase in memory usage or does it release it later on its own? I have seen the client increase memory usage on macOS only to release it later.
Re: possible memory leak then 'resources not found'
Posted: Sun Jun 15, 2025 3:00 am
by arisu
It seems permanent to me. The CPU usage for the client goes up to 100% for several seconds as the memory rapidly rises before it stops rising and CPU usage goes back down to <1%. I cannot imagine what could possibly be making it do that. The client has no need for that much memory.