System crashes on high mem usage Steps to reproduce Open you fav browser Open a Youtube video and 4 tabs of google docs Check system monitor for ram usage Wow. 98.8% and only 10% swap used??? Open one more tab System crash, have to reboot by holding power button
Expected result The memory is freed by swapping more files onto my swap partition Tested bug on -Opensuse Leap 15.0 -Fedora 28 -Ubuntu 18.04 -Manjaro Linux (latest version) Specs -CPU core 2 duo e6400 (usage is not high when the system crashes) -2.9 (3gb) Elpida ddr2 ram 533 MHz -Gnome 3.26 and 3.28 -Ati x1300 Gpu -3.0 gb swap partition Open a few more google docs tabs and crush my other computer with -CPU i5-520M -3.9 (4gb) Ram -Gnome 3.28 -Intel Igpu -4gb swap -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: System freeze on high memory usage Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in Fedora: Confirmed Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
