3 ms·
There's a fix for that. Unfortunately it needs to be reapplied on every reboot: sudo sh -c "echo 1000000 > /proc/sys/vm/max_map_count"
by 3836293648 4y ago
There's a fix for that. Unfortunately it needs to be reapplied on every reboot:
sudo sh -c "echo 1000000 > /proc/sys/vm/max_map_count"
- pritambaral 4y agoThat's a sysctl config (any path under /proc/sys/ is). See `man sysctl` for how to make it permanent (i.e., auto-apply it on boot). Here's an example: echo vm.max_map_count=1000000 | sudo tee /etc/sysctl.d/max_map_count.conf sysctl -f /etc/sysctl.d/max_map_count.conf Besides, there's plenty of ways to automatically execute any command on boot.
- happymellon 4y agoExcuse my ignorance, but would this be caused by a memory leak or an application that allocated an amount of memory allowed by Windows but not Linux, or something else?
- 3836293648 4y agoWhile we can basically allocate almost infinite memory due to swapfiles storing unused pages when they cannot fit into RAM any more, we still have a limit on how many allocations you can do. The game crashes because it tries to do too many allocations. It still uses a reasonable (ish) amount of memory, it's just way too many tiny chunks of memory that aren't allocated next to eachother
- happymellon 4y agoThank you, but wouldn't this be a problem on Windows then, or is Windows just more forgiving for this type of behaviour?