possible memory leak then 'resources not found'
Moderators: Site Moderators, FAHC Science Team
Re: possible memory leak then 'resources not found'
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.
-
- Posts: 1818
- Joined: Sun Dec 16, 2007 6:22 pm
- Hardware configuration: 9950x, 7950x3D, 5950x, 5800x3D
7900xtx, RX9070, Radeon 7, 5700xt, 6900xt, RX 550 640SP - Location: London
- Contact:
Re: possible memory leak then 'resources not found'
It's ok, we have reproducible scenario, so Dev can work on it
Re: possible memory leak then 'resources not found'
I'll run the client under heaptrack for a few days and see if I can glean anything useful from it.
-
- Posts: 1818
- Joined: Sun Dec 16, 2007 6:22 pm
- Hardware configuration: 9950x, 7950x3D, 5950x, 5800x3D
7900xtx, RX9070, Radeon 7, 5700xt, 6900xt, RX 550 640SP - Location: London
- Contact:
Re: possible memory leak then 'resources not found'
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'
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.
-
- Site Admin
- Posts: 8155
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4 - Location: W. MA
Re: possible memory leak then 'resources not found'
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'
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.