2 ms·
The problem in this case is deeper. The Linux kernel overcommits memory. OOMD is a workaround for this behaviour. And it can't be disabled. I disabled the ker
by Shorel 4y ago
The problem in this case is deeper. The Linux kernel overcommits memory.
OOMD is a workaround for this behaviour.
And it can't be disabled. I disabled the kernel memory overcommit and then neither Chrome nor Edge were running.
I can't use my computer without my browser of choice. Therefore, overcommit can't be disabled.
- bcrl 4y agoMaybe the problem is with the bloated apps that don't free memory? You can't blame the kernel for that. I routinely see Firefox consuming 10GB of RAM on my Linux desktop. It's nuts.
- chlorion 4y agoChrome and Edge not functioning without overcommit is not the fault of the kernel though. The browsers will allocate more memory than is physically available in the system but often not "touch" it. Without over-commit this causes an OOM situation and the kernel kills the browser, but that's what it's supposed to do when over-commit is disabled! I believe some of these massive allocations are used for security purposes or somehow related to the chromium sandbox but I can't remember exactly what's going on. Some sanitizers like ASAN do something similar for detecting invalid memory accesses (and hence can't be used without over-commit either)!