Closed Bug 168033 Opened 23 years ago Closed 20 years ago

resizing of jpeg takes way too much time

Categories

(Core :: Graphics: ImageLib, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: crh, Assigned: pavlov)

References

()

Details

(Keywords: platform-parity)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 In the URL included, there are several moderate sized jpeg files ( 640x480 ) When you visit the page the HTML calls for the files to be resized. This takes an extraordinary amount of time ( 3-4 seconds ) on a Pentium 4 2.0GHz Simply viewing the images seperate from the page displays the files very quickly. I'm not 100% sure that the resizing is the culprit. There is alot of javascript in there and turning off java script does seem to speed the page up but only trivially... maybe 1 second difference. Anyway. It looks ot me that the resizing is the bottleneck. There is no slowdown in I.E. (grumble grumble ) Reproducible: Always Steps to Reproduce: 1.go to the webpage in Mozilla 2.contrast to I.E. 3. Actual Results: Very slow rendering of all pictures. Even when hitting back button and and hten forward again. very slow Expected Results: The resizing should not have taken so long, and/or going back to the pacge a seocnd time should have cached the resized image.
Page loads nearly instantly on a P4 1.7Ghz linux machine...
Keywords: pp
Forgot to mention that this bug is windows specific.
It also appears to be P4 specific. I tried it on a K6-2 system and had no problems but saw the same results on anoter P4. Probably a compile time optimization gone awry?
cant see that problem on that page, but can reproduce it on http://forum.mokkels.nl/cgi-bin/gallery.pl?hold=1&action= scaled and loaded images lag alot while loading and even AFTER their loaded !?
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: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.