Closed
Bug 207553
Opened 21 years ago
Closed 19 years ago
Crash occurs when loading BMP image with image resizing enabled
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: chrispetersen, Assigned: jdunn)
References
()
Details
(Keywords: crash, regression)
Attachments
(1 file)
9.35 KB,
text/plain
|
Details |
Build: 2003-05-28-05 Platform: OS X Expected Results: Image should load and scale in window What I got: Application crashes Steps to reproduce: 1) Launch browser and create a new profile. (Automatic image resizing will be enabled by default) 2) After the browser window opens, paste this address into url field and press return: http://mozilla.org/quality/browser/front-end/testcases/imaging/images/Summer.bmp 3) Instead of loading and scaling this image, the application crashes
Reporter | ||
Comment 1•21 years ago
|
||
Comment 2•21 years ago
|
||
per the stack trace, this is mac-specific GFX code. cc'ing some mac people.
Component: ImageLib → Image: GFX
Reporter | ||
Comment 3•21 years ago
|
||
Agreed. This appears to be a Mac only issue since I can't reproduce using the 2003-05-27-08 Win32 build under WinXP.
Component: Image: GFX → ImageLib
Reporter | ||
Updated•21 years ago
|
QA Contact: tpreston → petersen
Comment 4•21 years ago
|
||
2003052307/OS X [trunk]... New profiles don't have image resizing on by default (thank god)... however I failed to repro the crash with or without image resizing... mulitple attempts include different window sizes and resizing the window with a scaled image. I'll grab a newer build in a bit and see if its a regression or just something that WFM
Reporter | ||
Comment 5•21 years ago
|
||
Ok, it appears this feature isn't enabled by default. However, I can reproduce this problem with the 2003-05-29-08 Macho trunk build. Here are my steps: 1) Launch and create a new profile in Mozilla 2) After window opens, go to Mozilla - Preferences. Check on 'Resize large images to fit in the browser window' under Appearance. Click OK. 3) Now, load the specified url in this report 4) As the image is loading and scaling, resize the window the larger and then smaller. 5) These steps tend to reproduce the crash (for me) after resizing this window multiple times.
Comment 6•21 years ago
|
||
ok... with a bit more steing i am now able to reproduces this semi-regularly in both 2003052307 and the 1.4rc1 builds. while i had no luck at all getting the crash resizing the window using the drag handles in the bottom left to the window during load i can get this crash consistantly if i hit shift-reload on the image and then use the maximize button to resize the window.
since I can only create this with automatic image resizing enabled, I am cc'ing mstolz. (I wonder if *people* are playing with the bits at the same time???)
Reporter | ||
Updated•21 years ago
|
Keywords: regression
Comment 9•20 years ago
|
||
This happens for me on : Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040321 Firefox/0.8.0+ Brings up the download window rather than rendering the image in firofox.
Comment 10•20 years ago
|
||
Okay, the URL original supplied seems to be serving hosed mime types so it isn't recognised as a BMP image. Replaced with a google image search for various BMP. Tried three different images from this search (including one 1912 x 3150 pixels - 994k) and all scale correctly in the latest nightly (2004033005) on 10.3.2. Can happily resize the window repeatedly so that images rescale. No problems.
Comment 11•20 years ago
|
||
a debian user reported a file that maybe trying to exploit this crash on windows: see http://bugs.debian.org/248857 for more info on this issue. Maybe someone can verify if this is truly an exploit.
Comment 12•20 years ago
|
||
alexander, you are probably seeing bug 243511. that one was not exploitable, afaik.
Comment 13•20 years ago
|
||
Bug 275120 might be related to (or even a duplicate of) this one. People CC'ed here might want to have a look.
Comment 14•19 years ago
|
||
This appears to be fixed by the Quartz image patch (Bug 245407). Confirm?
You need to log in
before you can comment on or make changes to this bug.
Description
•