Closed Bug 528832 Opened 16 years ago Closed 16 years ago

TopCrash [@nsPresContext::MediaFeatureValuesChanged(int) ]

Categories

(Core :: Layout, defect, P2)

1.9.2 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla1.9.3a1
Tracking Status
status1.9.2 --- beta4-fixed

People

(Reporter: cbook, Assigned: dbaron)

References

Details

(Keywords: crash, topcrash, Whiteboard: [crashkill][needs landing])

Crash Data

Attachments

(1 file)

Whiteboard: [crashkill]
Just looking at the stack seems to point at bug 522149 which added the line in frame 1 between beta 1 and 2.
I pulled the minidump for http://crash-stats.mozilla.com/report/index/96495f53-77ae-40e0-8bf1-b34042091116 and confirmed that the problem is that mShell is null. (Amusingly, nsPresContext::mShell and nsIPresShell::mStyleSet are at the same offset, 0xc.)
Flags: blocking1.9.2? → blocking1.9.2+
Attached patch patchSplinter Review
I suppose I could null-check at the caller, but I may as well null-check inside here.
Assignee: nobody → dbaron
Status: NEW → ASSIGNED
Attachment #412737 - Flags: review?(bzbarsky)
Comment on attachment 412737 [details] [diff] [review] patch We really need to get these object lifetimes sorted. :(
Attachment #412737 - Flags: review?(bzbarsky) → review+
Yeah. The PresShell/PresContext merge would be a good way to make sure this never happens...
Whiteboard: [crashkill] → [crashkill][needs landing]
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
OS: Windows Vista → All
Priority: -- → P2
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.3a1
Crash Signature: [@nsPresContext::MediaFeatureValuesChanged(int) ]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: