Assertion failure: aFirst && aSecond (Don't pass null pointers!), at caps/src/nsScriptSecurityManager.cpp:941

RESOLVED FIXED in mozilla27

Status

()

Core
Security: CAPS
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: dbaron, Unassigned)

Tracking

({assertion, crash})

Trunk
mozilla27
x86_64
Linux
assertion, crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

4 years ago
While using https://twitter.com/ (I think I was trying to search for a user in the box at the top), I hit the fatal assertion:

Assertion failure: aFirst && aSecond (Don't pass null pointers!), at /home/dbaron/builds/ssd/mozilla-central/mozilla/caps/src/nsScriptSecurityManager.cpp:941


Might not be caps's fault, though, given the massive instability in builds today.
(Reporter)

Comment 1

4 years ago
Created attachment 805605 [details]
end of browser output and a bit of gdb use
(Reporter)

Comment 2

4 years ago
Hit it a second time, just loading https://twitter.com/
So, this is happening because the old-fashioned mechanism for accessing object principals (which we invoke in debug builds to check our results) is returning null for some reason. I'm mildly curious to know why, but I think this code can also just go away. I'll attach a patch.
Created attachment 806087 [details] [diff] [review]
Remove old-style object principal calculation. v1
Attachment #806087 - Flags: review?(bzbarsky)
Comment on attachment 806087 [details] [diff] [review]
Remove old-style object principal calculation. v1

r=me
Attachment #806087 - Flags: review?(bzbarsky) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/68f90745d4b1
https://hg.mozilla.org/mozilla-central/rev/68f90745d4b1
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
You need to log in before you can comment on or make changes to this bug.