The default bug view has changed. See this FAQ.

Don't nuke chrome->chrome cross-compartment wrappers

RESOLVED FIXED in mozilla15

Status

()

Core
XPConnect
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: bholley, Assigned: khuey)

Tracking

unspecified
mozilla15
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

In bug 695480, we added code to nuke cross-compartment wrappers to dying scopes. This messed up compartment-per-global, but hopefully only because we now have many system compartments (instead of only one). Bug 695480 was mostly about killing chrome->content memory leaks, so we can hopefully just bail on the chrome->chrome wrapper case.

Kyle wrote the patch, which I'll attach and push to try momentarily.
Pushed to try with c-p-g: https://tbpl.mozilla.org/?tree=Try&rev=e0ff4a8c8098
We should consider bailing on the content-to-content case too, if we don't already, since that one would affect web-visible behavior.
We bail in the content->* case already.
Created attachment 619563 [details] [diff] [review]
Don't nuke chrome->chrome cross-compartment wrappers.
Attachment #619563 - Flags: review+
Pushed to m-i:
http://hg.mozilla.org/integration/mozilla-inbound/rev/a25ce1b3edf8
Target Milestone: --- → mozilla15
https://hg.mozilla.org/mozilla-central/rev/a25ce1b3edf8
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.