Closed
Bug 1548216
Opened 6 years ago
Closed 6 years ago
Crash in [@ mozilla::dom::BrowsingContext::RestoreChildren]
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 1547911
People
(Reporter: euthanasia_waltz, Unassigned)
Details
This bug is for crash report bp-1cd6e5ca-7ffe-45ef-a726-3a2fd0190501.
Top 10 frames of crashing thread:
0 xul.dll mozilla::dom::BrowsingContext::RestoreChildren docshell/base/BrowsingContext.cpp:338
1 xul.dll nsresult nsDocShell::RestoreFromHistory docshell/base/nsDocShell.cpp:7872
2 xul.dll nsresult nsDocShell::RestorePresentationEvent::Run docshell/base/nsDocShell.cpp:7310
3 xul.dll nsresult mozilla::SchedulerGroup::Runnable::Run xpcom/threads/SchedulerGroup.cpp:295
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1180
5 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
6 xul.dll void mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:88
7 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:308
8 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
9 xul.dll nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
STR:
- Start nightly with new profile
- Install ad blocker add-on (uBlock Origin or AdBlock Plus or AdGuard AdBlocker)
- Open https://old.reddit.com/r/firefox/new/
- Go to another site (www.yahoo.com, edition.cnn.com, www.bbc.com, twitter.com/FirefoxNightly, ...)
- Go back
I'm having this crash only on https://old.reddit.com/r/firefox/new/. (https://www.reddit.com/r/firefox/new/ doesn't have this issue)
Some sites(for step.4) don't cause crash. (www.tokyo-np.co.jp, www.yahoo.co.jp, www.ghacks.net, github.com/mozilla, ...)
Comment 1•6 years ago
|
||
Thanks for filing. This is a dupe of Bug 1547911 which was reopened.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Status: RESOLVED → VERIFIED
Crash Signature: [@ mozilla::dom::BrowsingContext::RestoreChildren]
QA Contact: Virtual
Updated•6 years ago
|
status-firefox68:
affected → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•