NixOS GNOME | 398 Members | |
| A room for maintainers of GNOME & GNOME-Related desktop environments (xfce, cinnamon, pantheon...) | 92 Servers |
| Sender | Message | Time |
|---|---|---|
| 29 Mar 2025 | ||
| oh god, libsoup_2_4 has over 3k rebuilds going into gst_plugins_bad via libnice | 08:33:23 | |
| https://github.com/NixOS/nixpkgs/issues/360897 | 10:52:52 | |
In reply to @k900:0upti.meI think we have three? | 12:40:16 | |
| the ISO has two of them | 12:40:23 | |
| ah that was mentioned | 12:42:00 | |
| Not very soon, but that is because I couldn't get the laptop to not heat up after second lock in during the day (I think some notification wake it up every time), so it either dies or I turn it off (otherwise it switches to default settings, which is insane behavior). But during all these days nothing has changed and the RAM usage gets bigger with time. Though the issue is that I still have around 22% RAM left and a ton of swap (and idle CPU), and now any task becomes super sluggish and the OS starts to freeze. Just a few moments ago I was just editing a file in Neovim and boom...now the GUI is frozen and only music is playing like nothing has happened. (The uptime is about 3.3 days.) So I had to hard power off again. Previously when this happened I also had about 75% RAM used, but then it all froze during loading of a web page in Firefox. As a result, there are absolutely no signs of why the system just suffocates over time, as all regular indicators show that it should work just fine. Other than ever growing RAM usage, yet there is still plenty of it left when the GUI freezes indefinitely. Since the music is still playing, I think that it's definitely something to do with gdm/mutter. And I'm on 6.13.7, actually. Cc K900 | 18:08:28 | |
| If you update to latest nixos-unstable, we should have memory allocation accounting enabled by default now | 18:09:09 | |
So you can use /proc/allocinfo to find out what's using the memory in the kernel | 18:09:23 | |
| Can you explain what it shows? | 18:10:08 | |
| a PID of each process and how much RAM it uses? | 18:10:38 | |
| https://docs.kernel.org/mm/allocation-profiling.html | 18:10:45 | |
| * a PID of each process and how much RAM it uses (in kernel)? | 18:10:47 | |
| thanks | 18:18:05 | |
| I think I will make a logger for it, so that I can see changes over time. | 18:22:30 | |
| This shows 15.02 GiB while only around 200 MiB is free:
Does this mean that it shows cumulative sum of used+cached memory? | 19:27:41 | |
| It shows specifically kernel allocations | 19:28:48 | |
| Not userspace processes | 19:28:51 | |
| But memory used within the kernel | 19:28:56 | |
| Which means that I indeed can actually see what is using how much.. | 19:28:58 | |
| But I only have 15 GiB of RAM. | 19:29:21 | |
| Are there any outliers there? Maybe lines that take up most of the memory? | 19:29:22 | |
| * But I only have 15 GiB of RAM. Which means no memory left for userspace stuff | 19:29:46 | |
| Over 10 MiB:
| 19:31:06 | |
| Weird that now cache is very big from the start (or after a few minutes). | 19:32:39 | |
| 5GB of readahead looks a bit too much, but that should be released as necessary | 19:33:47 | |
| I guess you just need to wait for whatever is happening to happen again | 19:34:05 | |
| And look at the data then | 19:34:09 | |
| The only problem program I know is yandex-disk, that sits now at 1.1 GiB RAM. Very annoying, but I have too much stuff there that I can't transfer. It didn't do this before. | 19:35:14 | |
| It also uses at least 1 (maybe more) full CPU core when indexing, which can slow down the system. | 19:36:09 | |
| I set a 1 min loop for logging that whole file. I won't wait until my GUI dies again, which means I hopefully will have something to tell in 1 or 2 day. | 19:46:25 | |