| 7 Mar 2025 |
|  Qyriad changed their display name from Qyriad to qyriad. | 16:48:58 |
 Andrew | I guess sine gnome-shell wrapped now uses 1.3 GiB, that means that the leak issue from Pop!_OS still persists, probably. | 19:18:31 |
| Andrew | I'm not sure if I said it, but I did try a few weeks ago literally killing everything that I can, and it went from 22.3 GiB to 13.9 GiB. Literally absolute idle machine with no user apps running, no nothing. And it uses 13.9 GiB, which I think a big chunk of it was just cache from somewhere. But when I start everything, it uses about 6 GiB after reboot. So about 8 GiB of garbage appeared from somewhere and didn't wand to go away unless I restart. I also thing the user session reset was 4 GiB dropped, though then there is 4 more that only reboot will fix? | 19:59:20 |
| Andrew | Should I open an issue for this or is it so rare, that it's not reproducible on reproducible OS and it will be closed? | 20:00:22 |
| Andrew | Different projects treat such stuff differently. | 20:00:36 |
 K900 | You should figure out what is actually leaking memory | 20:01:06 |
| K900 | Like, have you found what process it's attributed to? | 20:01:14 |
| K900 | Or what | 20:01:21 |
| Andrew | How can I do that, when I killed everything and cache is still there? | 20:01:50 |
| K900 | What "cache is still there" | 20:03:00 |
| K900 | Are you looking at the stats in free? | 20:03:05 |
| K900 | See https://www.linuxatemyram.com/ | 20:03:15 |
| Andrew | I do use several apps that are electron, that suck so much memory over time and in general, but if I kill em, I assume everything related to them should be removed from the memory. | 20:03:23 |
| Andrew | The 8 GiB more RAM usage with no apps, than all apps running on the startup | 20:03:54 |
| Andrew | * The 8 GiB more RAM usage with no apps at all, than all apps running on the startup | 20:04:03 |
| K900 | Have you looked at htop | 20:04:08 |
| K900 | Or any other tool | 20:04:10 |
| K900 | To figure out WHAT is actually taking up RAM | 20:04:14 |
| K900 | Or are you just looking at free and trying to guess | 20:04:21 |
| Andrew | well, there aren't many other stats to look at | 20:04:26 |
| K900 | There's htop | 20:04:32 |
| K900 | And slabtop if you want to look at kernel allocations | 20:04:40 |
| Andrew | I use btop | 20:04:47 |
| Andrew | if only they SHOWED WHAT is actually taking up RAM. but all process are shown as if they are innocent. | 20:05:44 |
| K900 | OK cool does it show what process is using the memory | 20:05:45 |
| K900 | So it doesn't? Even when run as root? | 20:05:55 |
| Andrew | idk, may /proc/pid stuff can show more RAM usage details per process | 20:06:05 |
| Andrew | wait, how would this differ? | 20:06:45 |
| Andrew | will it unlock hidden processes in btop? | 20:06:57 |
| K900 | It may show some additional kernel threads | 20:07:09 |
