Compartment mismatch with error page, javascript: URL, exception

RESOLVED FIXED

Status

()

Core
XPConnect
--
critical
RESOLVED FIXED
7 years ago
3 years ago

People

(Reporter: Jesse Ruderman, Assigned: gal)

Tracking

(Blocks: 1 bug, {assertion, testcase})

Trunk
x86
Mac OS X
assertion, testcase
Points:
---

Firefox Tracking Flags

(blocking2.0 final+)

Details

(Whiteboard: [hardblocker][has patch])

Attachments

(3 attachments)

(Reporter)

Description

7 years ago
Created attachment 508999 [details]
testcase (must be local)
(Reporter)

Updated

7 years ago
Group: core-security
(Reporter)

Updated

7 years ago
blocking2.0: --- → ?
(Reporter)

Comment 1

7 years ago
Created attachment 509000 [details]
stack trace
Andreas, do you have cycles for this?
Assignee: nobody → gal
blocking2.0: ? → final+
Whiteboard: [hardblocker]
(Assignee)

Comment 3

7 years ago
My plate is getting full but we can rebalance as we go along. Keep assigning this class of bugs to me.
(Assignee)

Comment 4

7 years ago
Created attachment 509295 [details] [diff] [review]
patch

I can't reproduce this but I think I can see the bug. Jesse, can you test the patch for me?
(Assignee)

Updated

7 years ago
Attachment #509295 - Flags: review?(jst)

Updated

7 years ago
Attachment #509295 - Flags: review?(jst) → review+
(Assignee)

Updated

7 years ago
Whiteboard: [hardblocker] → [hardblocker][has patch]
(Reporter)

Comment 5

7 years ago
The patch fixes it for me :)
Fix landed:

http://hg.mozilla.org/mozilla-central/rev/bdb4c38c56de
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
When I attempt to use this testcase, I get a new table briefly opened and then it dismisses itself. That's it. Am I supposed to see something else here? (This is with the beta 10 build of Firefox 4.)
I see the same behavior in the beta 11 build, post fix, BTW.
(Reporter)

Comment 9

7 years ago
I assume you mean a new tab.  If you view the testcase's source, you'll see that's what it does :)

Assuming you used a debug build of Firefox, and used a local copy of the testcase, you can call the bug Verified.
Group: core-security
You need to log in before you can comment on or make changes to this bug.