Closed
Bug 1223774
Opened 10 years ago
Closed 10 years ago
crash in mozilla::dom::Console::Console on 2015-11-10 Nighty
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla45
| Tracking | Status | |
|---|---|---|
| firefox45 | --- | fixed |
People
(Reporter: emorley, Assigned: baku)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
|
1.55 KB,
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
This bug was filed from the Socorro interface and is
report bp-2b9a879b-fe32-4287-909b-5ea1e2151111.
=============================================================
I'd just opened:
https://github.com/mozilla/treeherder/pull/1138
And from there had used the travis status link (click the green link) to open in two background tabs, these two links:
https://travis-ci.org/mozilla/treeherder/builds/90495096
https://travis-ci.org/mozilla/treeherder/builds/90496913
Roughly a second later the crash occurred.
Windows 8.1 x64, but using the 32bit Nightly.
Today's Nightly (2015-11-10), built from https://hg.mozilla.org/mozilla-central/rev/cc473fe5dc512c450634506f68cbacfb40a06a23
e10s disabled
addons: adblock, noscript, and a couple of others (see crash report metadata page)
| Reporter | ||
Comment 1•10 years ago
|
||
s/green link/green tick icon/
Comment 2•10 years ago
|
||
Hmm, null + offset crash? We get a null outer window, but I don't even pretend to understand the
wrapper setup we have here. AddonWrapper, CrossCompartmentWrapper and Proxy. Where are we dealing with outer window, where inner, or always inner or what?
Comment 3•10 years ago
|
||
It's quite odd to have a null outer on an inner. How can that happen?
Flags: needinfo?(khuey)
Comment 4•10 years ago
|
||
Though I guess FORWARD_TO_OUTER_OR_THROW null-checks the outer. Not sure whether that's just paranoia or justified.
There's lots of null-checking of mOuterWindow in nsGlobalWindow. I don't think it's just paranoia. But it's not clear to me how it can happen other than via unlinking.
Flags: needinfo?(khuey)
| Reporter | ||
Comment 6•10 years ago
|
||
And again:
bp-e704f503-9d2f-4a41-9b26-7b6a32151123
| Assignee | ||
Comment 7•10 years ago
|
||
Attachment #8690804 -
Flags: review?(bugs)
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → amarchesini
Comment 8•10 years ago
|
||
Comment on attachment 8690804 [details] [diff] [review]
console.patch
>+ if (!outerWindow) {
>+ mOuterID = outerWindow->WindowID();
>+ }
I'm pretty sure you don't want that '!' ;)
That fixed, r+.
So is something keeping a weak-ref-ish thing to inner window and using Window object after unlinking or
or perhaps something isn't unlinking everything properly and ends up handing already unlinked inner window to JS or...
I wonder if we should make WrapObject to fail on inner windows which don't have outer.
Attachment #8690804 -
Flags: review?(bugs) → review+
Comment 10•10 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox45:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•