Carlo Cabanilla <[email protected]> writes: > I don't have swap enabled. It's usually a dev virtualbox vm I'm > running that goes berserk and I can't click on anything or even move > my mouse until eventually I think something kills the vm process.
This means that problem is not in awesome, because awesome is not in charge of cursor movements , i suspect that you encountered notorious 12309 kernel bug (https://bugzilla.kernel.org/show_bug.cgi?id=12309) > > I was looking into using the magic SysRq key to kill the offending > process but it only can kill everything and it's kind of a pain when X > dies. > > .Carlo > > On Thu, Aug 27, 2015 at 4:47 PM, Aleksei <[email protected]> wrote: > > Carlo Cabanilla <[email protected]> writes: > > > Is there a good way of keeping awesome responsive even when > certain > > clients are using up all the cpu? Maybe something clever with > cgroups? > > Dear Carlo, usually Linux manages cpu usage quite well, preventing > freezes by dynamically increasing priority for low cpu consuming > processes (such as awesome wm). Which clients reduce > responsiveness ? > > I suppose that responsiveness issues caused by some other reasons, > for > example by swapping, or by using slow widgets in awesome. Have you > tried > to disable all third party widgets in awesome ? -- To unsubscribe, send mail to [email protected].
