Comment 95 for bug 226470

Those "window unexpectedly destroyed" messages start showing up shortly after the X server starts to get sluggish, that's the reason I got here in the first place.

In my case there are no other CPU or memory-hungry processes on the machine. Nor am I watching any videos inside a browser when the problems occur. And as I noted before, the problem doesn't just affect browser windows - in Seamonkey once things start going wrong, any window can be affected, e.g. the Print Status dialog, different panes in the MailNews module, etc. have all been affected at various times.

If Window *destruction* is the root cause of the problem, then why is the visible effect disrupting window *creation/rendering* ?

I think you're just chasing a symptom here, and you really need to find out why the CPU usage got to this bad state in the first place.