My personal workaround if I know I am doing something risky in respect to memory usage is to disable swap. The unresponsiveness than still kicks in (why is that either?) but the oom killer invents and bring down the runaway application and restores system usability, or the application kills itself on some memory allocation.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447052 Title: System should never drive into unresponsive swapping by naive end-user handling operations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447052/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
