Crash in [@ mozilla::dom::TabParent::Destroy]
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox65 | --- | unaffected |
firefox66 | - | wontfix |
firefox67 | --- | fixed |
firefox68 | --- | fixed |
People
(Reporter: calixte, Assigned: rhunt)
References
(Blocks 1 open bug)
Details
(Keywords: crash, regression, Whiteboard: [adv-main67+])
Crash Data
This bug is for crash report bp-611f1ae6-3544-400e-b1a6-87b7d0190224.
Top 10 frames of crashing thread:
0 xul.dll mozilla::dom::TabParent::Destroy dom/ipc/TabParent.cpp:372
1 xul.dll nsFrameLoaderDestroyRunnable::Run dom/base/nsFrameLoader.cpp:1615
2 xul.dll mozilla::dom::Document::MaybeInitializeFinalizeFrameLoaders dom/base/Document.cpp:6046
3 xul.dll nsresult mozilla::detail::RunnableMethodImpl< xpcom/threads/nsThreadUtils.h:1171
4 xul.dll nsDocumentViewer::Destroy layout/base/nsDocumentViewer.cpp:1845
5 xul.dll nsDocShell::Destroy docshell/base/nsDocShell.cpp:4956
6 xul.dll nsWebBrowser::SetDocShell toolkit/components/browser/nsWebBrowser.cpp:1283
7 xul.dll nsWebBrowser::InternalDestroy toolkit/components/browser/nsWebBrowser.cpp:200
8 xul.dll nsWebBrowser::Destroy toolkit/components/browser/nsWebBrowser.cpp:954
9 xul.dll WindowlessBrowser::Close xpfe/appshell/nsAppShellService.cpp:420
There are 8 crashes (from 8 installations) in 66.0b10 with buildid 20190221160854. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1516425.
The crash address is always: 0xe5e5e5e5.
[1] https://hg.mozilla.org/releases/mozilla-beta/rev?node=820b728e1ebe
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
It looks like the patch from bug 151425 that was trying to paper over the crash only shifted it to this signature. The root cause is still causing problems.
Comment 2•5 years ago
|
||
Ryan, is this just a dupe of bug 1516425 and we need to re-open that issue? Is 1516425 incomplete? Since it is on Beta, we need to figure that out soon.
Reporter | ||
Comment 3•5 years ago
|
||
[Tracking Requested - why for this release]:
The next release is the 2019-03-19 and we probably don't want to ship that bug.
Assignee | ||
Comment 4•5 years ago
|
||
Yes, this is a duplicate of bug 1516425. The special paper-over patch for Beta 66 didn't resolve the issue in Beta.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•11 months ago
|
Description
•