Open Bug 240218 Opened 21 years ago Updated 9 years ago

pages in background tabs rendered even though they are not shown => unresponsive mozilla

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: sendmespam, Unassigned)

References

Details

(Keywords: perf)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040401 Debian/1.6-4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040401 Debian/1.6-4 Just a little feature that would really help me when browsing eg. newssites (like http://www.heise.de/newsticker/ ): A preferences button to turn off/turn on rendering of pages that are not shown at the moment, because they are in another (unshown) tab. I dont know about you, but when I open a news site, I tend to ctrl-click all interesting links and read them lateron one by one. Mozilla is getting nearly unresponsive when a certain number of tabs is being rendered (this includes animated gifs, swf, etc.) in the background. Either a feature that stops rendering of background tabs when the machine's cpu limit is reached or a button to just turn off background rendering of tabs in Preferences would be really nice :) Reproducible: Always Steps to Reproduce: 1. ctrl-click a number of links (the number here is 13-15) 2. try ctrl-clicking more when the browser is getting increasingly unresponsive. 3. now start closing some of the background tabs while mozilla is unresponsive. 4. have fun ;-) Actual Results: mozilla got unresponsive (all of mozilla, not just the browser). Expected Results: - mozilla should have stopped background rendering of tabs if the cpu cant handle it. or - mozilla should have a button in eg. preferences to turn off rendering of tabs that are not visible (read: that are in the background)
I tried opening 70+ links at the same time, but no problem. CPU usage grows to 40-60% most of the time, 70% at most. P4 1.8MHz, WinXP, 20040410.
related/partly dup of: bug 120154, bug 145720, bug 177199, bug 227361, 235968 and perhaps related: bug 231891, 233780 There may be other issues invoved. For months now I had severe performance problems with Flash (on Linux) until i noticed the "appreg" file in my .mozilla dir was rather large. "strings appreg |grep lash |wc -l" and it returned 560 (It's a bug that was fixed long ago, but must have surfaced at some point - is OK again in current builds) What does the same commandline return on your version of the file? If a high number: quit moz, rename the file, restart moz (forcing appreg to be rebuilt) At this point Mozilla looses track of your existing profile names, but just type it in as if you create a new profile with the identical name, and all goes well. Take a backup of your bookmarks just in case.
Keywords: perf
i m getting a whooping "0" for appreg ;) the other bugs (most of which were supposedly fixed long ago) seem related.. especially the one with "shockwave keeps on rendering in the background tab". i noticed that www.heise.de/newsticker/ inserts a random shockwave ad into the newstext so shockwave rendering must be the culprit. has anybody found a way to stop shockwave from rendering when it s in the background already?
of these bugs: bug 120154, bug 145720, bug 177199, bug 227361, bug 235968 only bug 177199 is closed (as INVALID)
well some people in the threads of these bugs were talking about significant (positive) changes of the (supposedly) flawed behaviour in later versions of mozilla.. so i thought someone actually _did_ something about these (although the bugs arent closed, right).
*** Bug 242975 has been marked as a duplicate of this bug. ***
I would love to see Mozilla operate the same way OmniWeb on OSX does, in this respect. Everything is rendered and ready to go for the user but any animations/interactive elements (flash, animated gifs, java, etc) are not started until they're actually visible in the browser. You can see this if you load a page in OmniWeb with multiple copies of the same animated gif at diffrent places in the page. As you scroll down you will find that each copy of the gif is animated from a different starting point depending on when that particular copy was brought into the visual field. If it's not feasible to do this on such a granular level then doing it at the tab level would be good. This would save the the user from having to ctrl-tab to figure out which tab has just loaded an annoying flash with sound or embedded movie file.
Product: Core → SeaMonkey
Most of the things that can be done is probably core work, so marking as dependent on bug 595574.
Status: UNCONFIRMED → NEW
Depends on: 595574
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.