Closed Bug 1309958 Opened 3 years ago Closed 3 years ago
Crash while running ns
Plugin Instance Owner::Get Netscape Window during Interrupt Callback
I see 83 of these crashes in the last week (this signature, with that release assert).
Crash Signature: [@ nsWrapperCache::GetWrapper] → [@ nsWrapperCache::GetWrapper] [@ SandboxPrivate::GetGlobalJSObject ]
Summary: Crash in nsWrapperCache::GetWrapper during InterruptCallback → Crash while running nsPluginInstanceOwner::GetNetscapeWindow during InterruptCallback
[Tracking Requested - why for this release]: This is the number 3 top crash on Nightly Windows for 10-13.
One possible workaround may be not doing this if the page has a plugin instantiated on it? Generally it seems like we should have an assertion going off when getting to NotifyObservers() off of an interrupt callback. Basically arbitrary things can happen from that point on. :(
The problem here is that we're sending a sync message during painting, and from there we can run CPOW requests. I think we should try to mark any sync messages sent during painting as nested(inside_cpow). That way we'll never process CPOWs while waiting for a response. Instead, the parent will process these messages while waiting for its CPOW response. (Note that nested(inside_cpow) used to be prio(urgent) until we changed the name.)
Assignee: nobody → wmccloskey
Status: NEW → ASSIGNED
Attachment #8801405 - Flags: review?(mrbkap)
Duplicate of this bug: 1310843
Attachment #8801405 - Flags: review?(mrbkap) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/88b266698d18 Use urgent messages for stuff sent during painting (r=mrbkap)
This is another signature for this crash: bp-2efd8c50-d96f-40f3-8ce2-abf292161020 (From the Oct 19 Nightly which I'm pretty sure won't have the fix that landed in comment 9.)
Crash Signature: [@ nsWrapperCache::GetWrapper] [@ SandboxPrivate::GetGlobalJSObject ] → [@ nsWrapperCache::GetWrapper] [@ SandboxPrivate::GetGlobalJSObject ] [@ nsWrapperCache::GetWrapper const ]
You need to log in before you can comment on or make changes to this bug.