Question to #sysadmin out there: I regularly get #mariadb #oom-killed by Proxmox on LXC containers.

Has anyone else experienced this? Is it MariaDB-related? LXC-related?

Or need I to investigate more?

Interesting. #Synapse got #oom'ed. And I wasn't even doing anything with it.

On a 4gb VM...

#matrix #homeserver

Just enabled #zswap on banshee (@ndlug's VPS)... we'll see if helps with memory contention/pressure on our server.

#htop of before and after.

#oom

#zoom #ITmemes #memes #funny #OOM

Hmmmm still getting #OOM on my single user instance.

Out of #memory: Killed process 2925628 (bundle) total-vm:3612380kB, anon-rss:1498204kB, file-rss:0kB, shmem-rss:0kB, UID:991 pgtables:6484kB oom_score_adj:0

8Gb ram and 8Gb swap on my #RPI4 #mastodon instance #mastoadmin

#PyLance is so good, but crashes so often from #OOM. Why did they choose #TypeScript?

#PyLance is so good, but crashes so often from #OOM. Why did they choose #TypeScript?

Hm, turns out my backup failures were due to restic getting OOM killed. During the "forget" operation, not the actual backup, funnily enough. Digging through the docs now hoping to find something there. I can't (and generally don't want to) give it too much memory, as my backup is running as a Nomad job on each node, and there are other things running there as well.

#HomeLab #OOM

Huh!?

I'm trying to open qsv (csv toolkit written in #Rust) in VSCode and rust-analyzer keeps loading and loading until my 8GB RAM is full. 😬

What in the name of Ferris is happening!? :ferris:

There is a process "cc1plus" that allocates 6GB of RAM! Oh my!

Oh noes, it's C++!😵

Wait, what!? Have I just hit this weird UTF-16 bug in GCC?

https://stackoverflow.com/questions/29194247/how-to-diagnose-g-error-cc1plus-exe-out-of-memory-allocating-838860800-bytes

#OOM #OutOfMemory #Bug #GCC #CPlusPlus #UTF16 #UTF8 #Encoding

Coroot 0.11.0 now monitors memory usage and detects memory leaks before the #OOM killer invokes container restarts. https://buff.ly/3Y4ChAh #observability

More release speed-run updates in my Ops In Dev newsletter opsindev.news - subscribe at https://buff.ly/3XHVXtK 💡 #learntogether

Seit dem Serverumzug waren wir auf die unzureichende Toot-Länge vom 500 Zeichen zurückgeworfen worden. Jetzt wieder bei altbekannten 4096 (kurzzeitig sogar 4097 wegen Problemen #oom ).

#mastoadmin

On the topic of RAM, how many of you #rails devs are using the puma worker killer gem as a safeguard to prevent #OOM issues in production?

I have set it to kill processes at 90% of RAM usage.

I wonder what protection other devs are using, if any.

#puma #performance #memory

TIL that 16GB RAM + 8GB swap is still not enough for ESO which will happily gobble it all and sit there at 24 load average just daring the OOM to take it down. #games #oom #reboot

How To Kill The Largest Process In An Unresponsive #Linux System #OOM #OutOfMemoryKiller #EarlyOOM #Memory
https://www.ostechnix.com/kill-largest-process-unresponsive-linux-system/

I am using a visualization software that keeps using more and more memory as I load more data. I have 16 GB of RAM but there is more data than this.

I have increased vm.min_free_kbytes to 480000 but my machine keeps freezing if the memory is allocated slowly enough and the program is never killed.

What should I do? On top of being very annoying, it sounds like a severe security issue if any user can completely freeze the machine. It becomes too unresponsive to even connect to ssh.

#linux #memory #oom