Quoting Ivan Lazar Miljenovic <ivan.miljenovic at gmail.com>: > 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? ~d