User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 As far as I can tell switching to another tab (or minimizing/iconizing the mozilla window) should result in all processing in a given tab stopping. Ie. Java applets stopped, (gif) animation stopped, flash suspended, javascript as well, etc... Otherwise when you load up a single flash or animation intensive page it works ok, but as you start loading more of these in other tabs (which are obviously in the background) the entire system slows down, and not due to memory problems. It remains slow even after the pages have been downloaded and parsed. Basically everything on these pages keeps on running in the background - what ever for? Should be some option for suspending these background tasks. This is getting to be a greater and greater problem as animation and applets and javascipt get to be more and more everywhere and harder and harder to live without... Reproducible: Always Steps to Reproduce: open a few animation intensive flash inclusive pages Actual Results: everything slows to a halt Expected Results: there's no real reason for it to slow down - use memory yes, but slow down (assuming plenty of free ram)?

> Ie. Java applets stopped, (gif) animation stopped, flash suspended, javascript > as well, etc... I'm pretty sure there is no way to suspend plugins in the plugin API (the plugin itself would have to handle the suspending). In any case, this is all reported before.

(In reply to comment #1) > > Ie. Java applets stopped, (gif) animation stopped, flash suspended, javascript > > as well, etc... > > I'm pretty sure there is no way to suspend plugins in the plugin API (the plugin > itself would have to handle the suspending). > > In any case, this is all reported before. Well at _least_ java applets have stop and start methods which are meant to be called on minimize/maximize of the window, they're not called in mozilla on min/max and on tab switches...

see Bug 240218 with other bugs mentioned

*** This bug has been marked as a duplicate of 240218 ***