Closed Bug 1262342 Opened 9 years ago Closed 7 years ago

crash in XPCWrappedNativeScope::UpdateInterpositionWhitelist

Categories

(Core :: XPConnect, defect)

Unspecified
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED INACTIVE
Tracking Status
firefox47 --- wontfix
firefox48 --- wontfix
firefox-esr45 --- wontfix

People

(Reporter: n.nethercote, Unassigned)

References

Details

(Keywords: crash, Whiteboard: btpp-backlog)

Crash Data

This bug was filed from the Socorro interface and is report bp-b9e1c64a-9714-4651-93ff-730622160405. ============================================================= Nightly build 20160405030214 has 6 crashes like this one, making it the #2 cause of crashes for that build at the time of writing. In UpdateInterpositionWhitelist() is looks like |interposition| is null. The caller (XPCWrappedNativeScope::XPCWrappedNativeScope()) asserts that |mInterposition| is not null before passing, but maybe it's happening anyway? Perhaps a proper check rather than an assertion would fix this.
It appears to be a startup crash. All the uptimes are 0 or 1.
Most of the crashes were marked as dupes of one of them so I'm going to mark this as backlog for now.
Whiteboard: btpp-backlog
Crash volume for signature 'XPCWrappedNativeScope::UpdateInterpositionWhitelist': - nightly (version 50): 0 crash from 2016-06-06. - aurora (version 49): 0 crash from 2016-06-07. - beta (version 48): 11 crashes from 2016-06-06. - release (version 47): 20 crashes from 2016-05-31. - esr (version 45): 1 crash from 2016-04-07. Crash volume on the last weeks: Week N-1 Week N-2 Week N-3 Week N-4 Week N-5 Week N-6 Week N-7 - nightly 0 0 0 0 0 0 0 - aurora 0 0 0 0 0 0 0 - beta 0 5 1 4 1 0 0 - release 3 7 3 1 4 2 0 - esr 0 0 0 0 0 0 0 Affected platform: Windows
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.