crash in nsDocShellTreeOwner::AddChromeListeners() with window.closed property

RESOLVED WORKSFORME

Status

()

--
critical
RESOLVED WORKSFORME
5 years ago
3 years ago

People

(Reporter: martijn.martijn, Unassigned)

Tracking

({crash, testcase})

Trunk
All
Mac OS X
crash, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature, URL)

(Reporter)

Description

5 years ago
I've set the browser.tabs.remote preference to true in Firefox desktop, then when I go to the url testcase and click on the first button on that page, the pages are crashing.

I think this might be related/similar to bug 907795.

This bug was filed from the Socorro interface and is 
report bp-47d50988-85cf-4310-8e3b-db40d2131008.
=============================================================
0 	XUL 	nsDocShellTreeOwner::AddChromeListeners() 	embedding/browser/webBrowser/nsDocShellTreeOwner.cpp
1 	XUL 	nsDocLoader::FireOnProgressChange(nsDocLoader*, nsIRequest*, long long, long long, long long, long long, long long) 	/builds/slave/m-in-osx64-0000000000000000000/build/obj-firefox/x86_64/uriloader/base/../../../../uriloader/base/nsDocLoader.cpp
2 	XUL 	nsDocLoader::OnProgress(nsIRequest*, nsISupports*, unsigned long long, unsigned long long) 	/builds/slave/m-in-osx64-0000000000000000000/build/obj-firefox/x86_64/uriloader/base/../../../../uriloader/base/nsDocLoader.cpp
3 	XUL 	_ZThn32_N11nsDocLoader10OnProgressEP10nsIRequestP11nsISupportsyy 	/builds/slave/m-in-osx64-0000000000000000000/build/obj-firefox/x86_64/uriloader/base/../../../../uriloader/base/nsDocLoader.cpp
4 	XUL 	mozilla::net::HttpChannelChild::OnTransportAndData(tag_nsresult const&, unsigned long long, unsigned long long const&, nsCString const&, unsigned long long const&, unsigned int const&) 	netwerk/protocol/http/HttpChannelChild.cpp
5 	XUL 	mozilla::net::HttpChannelChild::RecvOnTransportAndData(tag_nsresult const&, unsigned long long const&, unsigned long long const&, nsCString const&, unsigned long long const&, unsigned int const&) 	netwerk/protocol/http/HttpChannelChild.cpp
6 	XUL 	mozilla::net::PHttpChannelChild::OnMessageReceived(IPC::Message const&) 	obj-firefox/x86_64/ipc/ipdl/PHttpChannelChild.cpp
7 	XUL 	mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) 	obj-firefox/x86_64/ipc/ipdl/PContentChild.cpp
8 	XUL 	mozilla::ipc::MessageChannel::DispatchAsyncMessage(IPC::Message const&) 	/builds/slave/m-cen-osx64-000000000000000000/build/obj-firefox/x86_64/ipc/glue/../../../../ipc/glue/MessageChannel.cpp
9 	XUL 	mozilla::ipc::MessageChannel::OnMaybeDequeueOne() 	/builds/slave/m-cen-osx64-000000000000000000/build/obj-firefox/x86_64/ipc/glue/../../../../ipc/glue/MessageChannel.cpp
10 	XUL 	MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask const&) 	/builds/slave/ux-osx64-000000000000000000000/build/obj-firefox/x86_64/ipc/chromium/../../../../ipc/chromium/src/base/message_loop.cc
11 	XUL 	MessageLoop::DoWork() 	/builds/slave/ux-osx64-000000000000000000000/build/obj-firefox/x86_64/ipc/chromium/../../../../ipc/chromium/src/base/message_loop.cc
12 	XUL 	mozilla::ipc::DoWorkRunnable::Run() 	ipc/glue/MessagePump.cpp
13 	XUL 	nsThread::ProcessNextEvent(bool, bool*) 	/builds/slave/ux-osx64-000000000000000000000/build/obj-firefox/x86_64/xpcom/threads/../../../../xpcom/threads/nsThread.cpp
14 	XUL 	NS_ProcessPendingEvents(nsIThread*, unsigned int) 	/builds/slave/ux-osx64-000000000000000000000/build/obj-firefox/x86_64/xpcom/build/../../../../xpcom/glue/nsThreadUtils.cpp
15 	XUL 	nsBaseAppShell::NativeEventCallback() 	/builds/slave/ux-osx64-000000000000000000000/build/obj-firefox/x86_64/widget/xpwidgets/../../../../widget/xpwidgets/nsBaseAppShell.cpp
16 	XUL 	nsAppShell::ProcessGeckoEvents(void*) 	widget/cocoa/nsAppShell.mm

Updated

3 years ago
Crash Signature: [@ nsDocShellTreeOwner::AddChromeListeners()] → [@ nsDocShellTreeOwner::AddChromeListeners()] [@ nsDocShellTreeOwner::AddChromeListeners]
I just tested this out and this no longer crashes.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.