Closed
Bug 487856
Opened 15 years ago
Closed 15 years ago
Crash [@ nsDisplayBackground::IsOpaque(nsDisplayListBuilder*) ]
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: florian, Unassigned)
References
()
Details
(Keywords: crash)
Crash Data
I just saw this stack (that doesn't look corrupted) and it seems to be in very recently added code in bug 482689. I have no idea about the steps to reproduce. 518 bottomLayer.mImage.mRequest->GetImage(getter_AddRefs(container)); 519 520 PRUint32 nframes; 521 container->GetNumFrames(&nframes); The crash happened on line 521. Is it possible that container is null after GetImage?
I would have thought this was fixed by http://hg.mozilla.org/mozilla-central/rev/8d5495c3449e Was your build from in the short interval between the original landing and the bustage fix? http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=683b00c3d1d1&tochange=8d5495c3449e
Given the code you're quoting... which was only in the tree in that interval, I'm going to say this was fixed by the changeset cited in comment 1.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ nsDisplayBackground::IsOpaque(nsDisplayListBuilder*) ]
You need to log in
before you can comment on or make changes to this bug.
Description
•