This web page causes the entirety of mozilla to slow to a crawl



16 years ago
13 years ago


(Reporter: phil, Unassigned)



Firefox Tracking Flags

(Not tracked)





16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2

Having this web page open in a mozilla window causes the entirety of the
mozilla GUI to slow to a crawl. Page downs of any page (not just the one) for instance take on the order of
10-20 seconds.

This is the case even if the backupbrain page is in a tab which is not the tab
currently being shown.

Reproducible: Always

Steps to Reproduce:
1. Visit
2. Observe mozilla UI turn to treacle

Comment 1

16 years ago
wfm using build 2003072704 on Win2k, no noticable slow down.

Comment 2

16 years ago
This is a rendering issue on a large background image. X is slow when
doing this doing it.

Reporter try this. In 


set the 

   Use my chosen background and image ignoring....


Then reload the page. Should be fine.
As a matter of fact, taking out the background image does not help things much,
for me.  Scrolling the page still pegs the CPU.

We need something like a testcase here....

Comment 4

16 years ago
Seems to work fine for me if i disable the background image, otherwise, it's
worth doing a 'wget' on the page to get a local copy (if you think the background
is not the problem) and decompose it, removing chunks until the page is back
to "normal".

Comment 5

15 years ago
Addendum: I've just realised that I was viewing this page doing this over
an sshed mozilla (on 100baseT ethernet), which obviously will exacerbate
Xserver / protocol issues. Even so, I don't think it should be
*this* slow.                                                                   
        Maybe I'm overoptimistic!

Regardless, this obviously isn't a mozilla priority -- when viewed
locally the page is much more snappy, although it's still noticably
slower than viewing other pages. Does Moz use the
RENDER extension when available to do this kind of compositing on the
server side, rather than doing it at the client side and shipping the
gif to the server? If not, is that a possible solution?

It does seem wrong however that switching *away* from the tab with the home page to a different tab takes a significant
length of time. Perhaps this is really an Xserver problem -- viewing
the page in the first place over the sshed mozilla does seem to tie up
the Xserver for a significant chunk of time.



Comment 6

15 years ago
Reporter can you retry your test with a new ckeckout build from today 
since bug 216430 has been fixed in the trunk which may be related to the
slugishness you were seeing. 

Please update/close this bug on you results.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.