Comment 92 for bug 226470

Something else I've noticed recently - as noted before, the problems don't start right away, they only start happening after mozilla has been running for a while. Over the course of time things run a lot more sluggishly. Just now I noticed in top that the X server was taking 16% of my CPU even though nothing was happening anywhere. The seamonkey binary was taking like 1%, nothing else was really taking anything. But when I exited seamonkey, the X server's CPU usage dropped back to 0.7%. So it appears that seamonkey is doing something weird that confuses the X server, and that's when things start going wrong.