Brandon S Allbery KF8NH writes:

On 6/19/10 08:59 , Ivan Lazar Miljenovic wrote:

...

Every now and then I find that Xorg suddenly uses a lot of CPU for a while, making xmonad non-responsive. In general, this seems to be a fault of either Firefox or Emacs (in that xrestop says Firefox is using the most responses but for me it usually becomes unresponsive whilst I'm using Emacs).

Emacs and many terminal emulators have this thing where they don't want to obey the window manager and try to resize themselves to their preferred size instead. Could this be it?

Could be; I've never managed to work out what the problem was. In this case, I've narrowed it down even further: I can run terminal with no problem, but as soon as I run top inside it it starts chewing up CPU (even if I quit top). -- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com IvanMiljenovic.wordpress.com

wagnerdm@seas.upenn.edu writes:

Quoting Ivan Lazar Miljenovic :

...

In this case, I've narrowed it down even further: I can run terminal with no problem, but as soon as I run top inside it it starts chewing up CPU (even if I quit top).

Does top use curses? Do other curses apps trigger this behavior?

Top does appear to use ncurses, but trying to run things like console emacs or ncdu doesn't result in the same kind of X usage (goes from 7% to 17%). -- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com IvanMiljenovic.wordpress.com