Frequently on some of my Ubuntu 10.04 machines I have a strange problem.
Some program will act up or break and need to be killed. But top will be frozen. Even if you close your session and come back days later top will still show the status of root processes the moment before the program acted up.
Killing the offending (broken) processes will free up system resources again, and you can use the machine like normal. EXCEPT the top command will be indefinitely frozen in the old state: for days, even weeks, on end.
Restarting the computer fixes top, but that doesn't help me understand what is going on.
What causes this scenario where top freezes? Is there a more clever way of fixing it than just restarting the machine?
topbehaves like you describe. In other words, you are asking what you would be asked by a bug triager. So I think the question is perfectly legitimate, and I would avoid reporting it as a bug till you have more information about it. – Andrea Corbellini Jan 10 at 19:51stracecan provide helpful information. The problem is thatstraceproduces way too output to be posted on Ask Ubuntu (which does not support attachments). Probably a bug report is better to handle the issue. :-) – Andrea Corbellini Jan 10 at 20:00