It's probably not fixed. bbordwell who closed it never bothered to test what he believed would be a fix, as far as I can tell. He just went with something he thought might be related that he read on Phoronix.
On the previous bug #27441 on this matter I provided a simple test program you can compile and use to reproduce the problem. I don't if that still reproduces it, but you can give it a try. BUT before you waste your breath and try reopening this, note that I reported that old bug many years ago, and it was closed repeatedly by people who never bothered to actually think about the problem. After 5 years, Tim Gardner came by, didn't read the description properly (so it seems from his closing remark) or tried my test program and closed it for good. So I would recommend against reopening. If you want to see this fixed, try to get some developers on the kernel mailing list interested in the problem. If you could get a solid test case going, e.g. with a VM with constrained memory and a simple script or program to run, I guess some people might see it as a fun challenge. Over the years I've come to the conclusion that the people in the other end of this bug tracker probably see it as a low-priority, long-running, hard-to-fix annoyance, and that's not the right starting point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/620074 Title: Thrashing turns system unusable To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/620074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
