3 ms·
I've had it trigger regularly, it fires far too late (if at all) and the system had already become unstable at the point in which it freezes. It should be firin
by bArray 3y ago
I've had it trigger regularly, it fires far too late (if at all) and the system had already become unstable at the point in which it freezes. It should be firing far earlier.
- arp242 3y agoYeah, the system locks up, but it should recover – eventually. You just need to go for a coffee, or bagel, or bowel movement, or wank, or whatever. At least, that's been my experience.
- bArray 3y agoNo, it doesn't always. There has been a few times I've left a machine for literal days (when I really needed it to recover) and it does not recover. My guess is that something causes a kernel panic, like the filesystem getting itself into trouble with the hardware.
- wongarsu 3y agoIf you have too much swap configured it can take hours to recover. Maybe days, never let it go that long without giving up. The kernel is terribly slow at swapping stuff back once memory pressure is gone. Of course the remedy is to have no or very little swap configured, but that's not obvious when compared to other operating systems (for example on Windows more swap never hurts, and the system recovers very quickly once memory pressure is gone)
- bArray 3y agoThat and there are some processes that should never be swapped, and yet they are. I think it should be possible for a process to request that it is never swapped, or to suggest sections of it are never swapped. Even a swap blacklist would be a great start.