Re: huge amount laundry memory not being cleaned up
Hi Pete, I run into the same issue around 4 weeks ago. This was with 13.2-p0. Been using the same setup for a few years and it the first time it happens to "run out of memory". The blame was also for plasmashell. Santi On 7/11/23 19:43, Pete Wright wrote: On 7/11/23 10:37 AM, Olivier Certner wrote: Le mardi 11 juillet 2023, 01:51:02 CEST Pete Wright a écrit : sorry for the noise folks, this is almost certainly an issue with my local env. this is helpful for me, as i'll have a better idea as to where i should focus my efforts trying to find this memory hog next time. I have had what I suspect to be the same issue on 13.2-STABLE with KDE and very long sessions. I say "suspect" since I seem to remember that laundry usage went down by unlogging (or restarting kwin or plasmashell), but I'm not completely sure now. So may not be specific to your local env after all, nor to CURRENT. Regards. oh interesting. i've found myself having to restart plasma once a week or so to fix some glitches with the tool bar. i just run: kquitapp5 plasmashell && kstart5 plasmashell so it's certainly possible thats where the issue lies. i'd try another window manager, but i really like plasma5 lol. maybe i'll take one for the team and run mate or xfce for a few weeks and see if see similar behavior. -pete
Re: huge amount laundry memory not being cleaned up
On 7/11/23 10:37 AM, Olivier Certner wrote: Le mardi 11 juillet 2023, 01:51:02 CEST Pete Wright a écrit : sorry for the noise folks, this is almost certainly an issue with my local env. this is helpful for me, as i'll have a better idea as to where i should focus my efforts trying to find this memory hog next time. I have had what I suspect to be the same issue on 13.2-STABLE with KDE and very long sessions. I say "suspect" since I seem to remember that laundry usage went down by unlogging (or restarting kwin or plasmashell), but I'm not completely sure now. So may not be specific to your local env after all, nor to CURRENT. Regards. oh interesting. i've found myself having to restart plasma once a week or so to fix some glitches with the tool bar. i just run: kquitapp5 plasmashell && kstart5 plasmashell so it's certainly possible thats where the issue lies. i'd try another window manager, but i really like plasma5 lol. maybe i'll take one for the team and run mate or xfce for a few weeks and see if see similar behavior. -pete -- Pete Wright p...@nomadlogic.org
Re: huge amount laundry memory not being cleaned up
Le mardi 11 juillet 2023, 01:51:02 CEST Pete Wright a écrit : > sorry for the noise folks, this is almost certainly an issue with my > local env. this is helpful for me, as i'll have a better idea as to > where i should focus my efforts trying to find this memory hog next time. I have had what I suspect to be the same issue on 13.2-STABLE with KDE and very long sessions. I say "suspect" since I seem to remember that laundry usage went down by unlogging (or restarting kwin or plasmashell), but I'm not completely sure now. So may not be specific to your local env after all, nor to CURRENT. Regards. -- Olivier Certner
Re: huge amount laundry memory not being cleaned up
On 7/10/23 4:26 PM, Pete Wright wrote: i'm doing a build world now since i'll need to reboot this box anyway, just to get everything up to date. interestingly enough i'm still pegged at 14G of laundry memory, and my 2G swap is %100 utilized. once the build world completes i'll do a double check and see if i can find any large consumers of resident memory which may lead me in the right direction. so...build world competed, and after quitting my kde5 session all of the laundry got free'd up right away. i suspect either firefox/chrome didn't exit cleanly, or there was something funky going on with kde. sorry for the noise folks, this is almost certainly an issue with my local env. this is helpful for me, as i'll have a better idea as to where i should focus my efforts trying to find this memory hog next time. -p -- Pete Wright p...@nomadlogic.org
Re: huge amount laundry memory not being cleaned up
On 7/10/23 4:01 PM, Mark Millard wrote: Pete Wright wrote on Date: Mon, 10 Jul 2023 19:35:26 UTC : hi there, i've got a workstation running CURRENT that recently ran out of swap space. i killed the usual suspects (chrome, firefox and thunderbird) and noticed some odd behavior. while some memory did get freed up - after leaving the system idle for 4 hours i still have 14G or memory in the Laundry according to top. I also have noticed that very little data has paged out of swap (100MB out of 2G). i was wondering if there was a good way to determine what is in the laundry, I do not know how to get a breakdown of the laundry's usage. But I'd expect, say, for example, top's resident memory figures would count what is in the laundry as resident. If correct, given the large laundry usage, may be some resident figures would be suggestive? thanks Mark, so yea i poked around and didn't see any large consumers of resident memory. or get diagnostic info on why it's not cleaning itself up? As I understand, it would take take one of the following to change the status of the pages in the laundry in normal operation: A) access to a page by a program, turning the page into being in the active category. (It might go through inactive to get there?) B) memory pressure leading to sending the page to the swap in order to provide a page for a different use. Time alone does not contribute much as I understand. More on-demand driven. Laundry is sort of "inactive but known to be dirty" as I understand, in some respects just a subset of inactive optimized for being closer to ready to page out to swap space if needed. i'm doing a build world now since i'll need to reboot this box anyway, just to get everything up to date. interestingly enough i'm still pegged at 14G of laundry memory, and my 2G swap is %100 utilized. once the build world completes i'll do a double check and see if i can find any large consumers of resident memory which may lead me in the right direction. cheers! -pete -- Pete Wright p...@nomadlogic.org
RE: huge amount laundry memory not being cleaned up
Pete Wright wrote on Date: Mon, 10 Jul 2023 19:35:26 UTC : > hi there, > i've got a workstation running CURRENT that recently ran out of swap > space. i killed the usual suspects (chrome, firefox and thunderbird) > and noticed some odd behavior. while some memory did get freed up - > after leaving the system idle for 4 hours i still have 14G or memory in > the Laundry according to top. I also have noticed that very little data > has paged out of swap (100MB out of 2G). > > > i was wondering if there was a good way to determine what is in the > laundry, I do not know how to get a breakdown of the laundry's usage. But I'd expect, say, for example, top's resident memory figures would count what is in the laundry as resident. If correct, given the large laundry usage, may be some resident figures would be suggestive? > or get diagnostic info on why it's not cleaning itself up? As I understand, it would take take one of the following to change the status of the pages in the laundry in normal operation: A) access to a page by a program, turning the page into being in the active category. (It might go through inactive to get there?) B) memory pressure leading to sending the page to the swap in order to provide a page for a different use. Time alone does not contribute much as I understand. More on-demand driven. Laundry is sort of "inactive but known to be dirty" as I understand, in some respects just a subset of inactive optimized for being closer to ready to page out to swap space if needed. > when i've seen this before only a reboot will get the system back to > being stable, if i re-launch my desktop apps they'll quickly start > trying to page out to disk again creating an OOM condition. > > system has 32G of RAM and is running this checkout > FreeBSD topanga 14.0-CURRENT FreeBSD 14.0-CURRENT #66 > main-n263884-d2a45e9e817a: Thu Jun 29 15:50:44 PDT 2023 === Mark Millard marklmi at yahoo.com
huge amount laundry memory not being cleaned up
hi there, i've got a workstation running CURRENT that recently ran out of swap space. i killed the usual suspects (chrome, firefox and thunderbird) and noticed some odd behavior. while some memory did get freed up - after leaving the system idle for 4 hours i still have 14G or memory in the Laundry according to top. I also have noticed that very little data has paged out of swap (100MB out of 2G). i was wondering if there was a good way to determine what is in the laundry, or get diagnostic info on why it's not cleaning itself up? when i've seen this before only a reboot will get the system back to being stable, if i re-launch my desktop apps they'll quickly start trying to page out to disk again creating an OOM condition. system has 32G of RAM and is running this checkout FreeBSD topanga 14.0-CURRENT FreeBSD 14.0-CURRENT #66 main-n263884-d2a45e9e817a: Thu Jun 29 15:50:44 PDT 2023 Cheers, -pete -- Pete Wright p...@nomadlogic.org
