
22 Jun
2010
22 Jun
'10
6:21 a.m.
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