Closed Bug 336659 Opened 19 years ago Closed 19 years ago

Slow render on a 50x50 table of pngs

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: bofh.kill.9.spam, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3 The URL link is to a page with a 50x50 table of the same small (94 b) PNG image. The page renders very slowly, and acts as though it downloads the image repeatedly. However, there is no network traffic during most of this time. The processor on my box is pinned at 100% while this page loads and renders. IE renders the page at a very fast rate. Reproducible: Always Steps to Reproduce: 1. Go to the URL mentioned in this report. 2. See how long it takes the page to complete loading. Actual Results: Slow render time, of about 10 seconds. Expected Results: Much faster render time (page is not complex, and the image is in cache)
Some notes: - This also happens with other image formats - This does only happen on some clients, it's not reproducable for everyone (depending on some specific settings?) - This does not happen when the image being accessed is stored on your local hd, thus it's not the image rendering itself, that is bugged.
It seems that on closer inspection, this isn't a Firefox bug, it has to do with Adblock testing each filter regex on each imange separately. I'll put a note in with the Adblock team notifying them of this slowdown.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
I don't use Adblock, and it still takes a few seconds for me. I do, however, have a lot of other extensions, including Flashblock, Greasemonkey and Platypus. I can give a detailed listing if needed. My User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
You need to log in before you can comment on or make changes to this bug.