|
Bugzilla – Full Text Bug Listing |
| Summary: | firefox crashes on streaming jpeg image | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Marcus Meissner <meissner> |
| Component: | Firefox | Assignee: | E-mail List <bnc-team-mozilla> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | federico, gnome-bugs |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
debug.log
simple testcase |
||
|
Description
Marcus Meissner
2005-12-20 21:25:33 UTC
Created attachment 61545 [details]
debug.log
debugging session on current autobuild state
with debuginfo and line numbers.
Do you have an public URL where this is done? So it happens for you with 1.0.7 on 10.0 and 1.5 on 10.1alpha? hmm, upstream Firefox 1.5 doesn't crash. I don't think that our patches are to blame but maybe some gtk issue. Created attachment 61686 [details]
simple testcase
It's a Mozilla bug. See the bottom of the log in comment #1; mImageBits is 0. It ends up passing "buf = 0" to gdkrgb. OK, do you have an idea why the upstream binary doesn't show this behaviour? Could it be because it's linked against older versions of gtk etc.? No idea. But GTK+ is not the problem here - it is getting passed a null pointer instead of a valid buffer. If you are testing that particular image, you could set a conditional breakpoint in gdk_draw_rgb_image_core() when rowstride==1032. Compare the stack traces for our version and the upstream version, and see what changed. looks like the nsImageGTK destructor was called, but the UpdateCachedImage() was called after that I've filed upstream bug 328684: https://bugzilla.mozilla.org/show_bug.cgi?id=328684 with a possible patch. I need some upstream feedback to be sure it's the right patch. My patch was accepted upstream. We can take it for our FF1.5 releases if we want to. Whether we do or not, this is fixed. I have it already in my local tree, thanks ;-) It will be submitted with next checkin for beta7 |