| 7 Mar 2025 |
Andrew | * Nothing feels better than 31 GiB of fully filled RAM and swap on an idle GNOME NixOS, after which earlyoom starts killing stuff. | 07:20:57 |
Andrew | * Nothing feels better than 31 GiB of fully filled RAM and swap on an idle Wayland GNOME NixOS, after which earlyoom starts killing stuff. | 07:23:37 |
K900 | You definitely have a memory leak somewhere and you should really figure out where tbh | 07:28:49 |
Andrew | tbh, I already asked about this and nothing came out of it, and figuring out by myself isn't easy. I have too little time to conduct research on who's the impostor. | 08:22:54 |
Andrew | If I will have time for this, might as well switch to Hyprland and hope the problem will go away. | 08:23:20 |
Andrew | I know that on X11 GNOME Pop!_OS there was a tiny memory leak and normally with time the gnome-shell process will eat more and more, but I think at worse it was about 600 MiB or something. But by far the worst issue was that the system start to have frequent and long freezes. So watching any video is pure pain. | 08:25:57 |
Andrew | Now I basically ported (almost) everything on NixOS plus switched to Wayland. Now I have a ton of small issues because GNOME doesn't implement anything from wlroots, but the freezes are mostly gone. They do show up probably because kswapd0 moves cache from time to time. But it's all good when there is plenty of RAM left. | 08:28:31 |
Andrew | Well, the GNOME is much more up-to-date too. So maybe with each version their leaks become increasingly bigger. | 08:29:30 |
Andrew | I once measured that overnight the increase was about 0.5 GiB or so. What can be a potential problem is that I close Firefox much more frequent, cuz before I used it for different stuff, now all of that are separated desktop apps. | 08:31:57 |
Andrew | well firefox and kitty+zellij | 08:32:14 |
Andrew | other than that, everything is just a regular routine. | 08:32:47 |
Andrew | Sucks that initially I fell in love with GNOME UI, and as the time went by, I hit more and more issues with it, and now it's the last thing I would recommend to anyone. | 08:35:20 |
Andrew | * Sucks that initially I fell in love with GNOME UI, and as the time went by (many years), I hit more and more issues with it, and now it's the last thing I would recommend to anyone. | 08:35:32 |
K900 | @Jan Tojnar around? | 12:33:59 |
K900 | We need x-d-p 1.20 on staging-next | 12:34:06 |
K900 | For pipewire 1.4 support | 12:34:10 |
K900 | I'm making a PR based off of https://github.com/NixOS/nixpkgs/pull/375498 | 12:34:41 |
K900 | https://github.com/NixOS/nixpkgs/pull/387894 | 12:38:54 |
| 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 |