[e10s] Tab crashes when loading the Loop invite in the location bar

RESOLVED INCOMPLETE

Status

()

Core
Graphics
--
critical
RESOLVED INCOMPLETE
4 years ago
a year ago

People

(Reporter: Loic, Unassigned)

Tracking

({crash})

34 Branch
x86_64
Windows 7
crash
Points:
---

Firefox Tracking Flags

(e10s-, firefox47 affected)

Details

(crash signature)

(Reporter)

Description

4 years ago
Maybe a dupe of bug 1053454 with a different crash signature.

STR:
1) Start Nightly (close your current session if need be)
2) about:config > browser.tabs.remote.autostart = true (restart Nightly)
3) Click on the bubble phone icon in the menu bar
4) Copy the link of the talk invite
5) Paste it in the location bar and press 'enter'

Result: tab crashes.

CR:
https://crash-stats.mozilla.com/report/index/085b034f-43d1-4579-909b-401d82140814

Frame 	Module 	Signature 	Source
0 	mozalloc.dll 	mozalloc_abort(char const* const) 	memory/mozalloc/mozalloc_abort.cpp
1 	xul.dll 	NS_DebugBreak 	xpcom/base/nsDebugImpl.cpp
2 	xul.dll 	mozilla::dom::PBrowser::Transition(mozilla::dom::PBrowser::State, mozilla::ipc::Trigger, mozilla::dom::PBrowser::State*) 	obj-firefox/ipc/ipdl/PBrowser.cpp
3 	xul.dll 	mozilla::dom::PBrowserChild::SendRemotePaintIsReady() 	obj-firefox/ipc/ipdl/PBrowserChild.cpp
4 	xul.dll 	mozilla::layers::CompositorChild::RecvRemotePaintIsReady() 	gfx/layers/ipc/CompositorChild.cpp
5 	xul.dll 	mozilla::layers::PCompositorChild::OnMessageReceived(IPC::Message const&) 	obj-firefox/ipc/ipdl/PCompositorChild.cpp
6 	xul.dll 	mozilla::ipc::MessageChannel::DispatchAsyncMessage(IPC::Message const&) 	ipc/glue/MessageChannel.cpp
7 	xul.dll 	mozilla::ipc::MessageChannel::DispatchMessageW(IPC::Message const&) 	ipc/glue/MessageChannel.cpp
8 	xul.dll 	mozilla::ipc::MessageChannel::OnMaybeDequeueOne() 	ipc/glue/MessageChannel.cpp
9 	xul.dll 	MessageLoop::RunTask(Task*) 	ipc/chromium/src/base/message_loop.cc
10 	xul.dll 	MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask const&) 	ipc/chromium/src/base/message_loop.cc
11 	xul.dll 	MessageLoop::DoWork() 	ipc/chromium/src/base/message_loop.cc
12 	xul.dll 	mozilla::ipc::DoWorkRunnable::Run() 	ipc/glue/MessagePump.cpp
(Reporter)

Updated

4 years ago
Blocks: 899758
Severity: normal → critical
Crash Signature: [@ mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::PBrowser::Transition(mozilla::dom::PBrowser::State, mozilla::ipc::Trigger, mozilla::dom::PBrowser::State*) ]
tracking-e10s: --- → ?
Keywords: crash
tracking-e10s: ? → -

Comment 1

4 years ago
The PBrowser being used here is either already deleted or a bogus pointer.
Component: IPC → Graphics
Edited the title so this will show up for searches looking for bugs in Loop.
Summary: [e10s] Tab crashes when loading the talk invite in the location bar → [e10s] Tab crashes when loading the Loop invite in the location bar
I hit this crash when operating Picasa in a non-e10s window combined with normal browsing (e.g. Bugzilla) in an e10s window. Pages in the e10s window had stopped loading and it eventually crashed. So it's not Loop specific.

Updated

2 years ago
Crash Signature: [@ mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::PBrowser::Transition(mozilla::dom::PBrowser::State, mozilla::ipc::Trigger, mozilla::dom::PBrowser::State*) ] → [@ mozalloc_abort(char const* const) | NS_DebugBreak | mozilla::dom::PBrowser::Transition(mozilla::dom::PBrowser::State, mozilla::ipc::Trigger, mozilla::dom::PBrowser::State*) ] [@ mozalloc_abort | NS_DebugBreak | mozilla::dom::PBrowser::Transition ]

Comment 5

2 years ago
Hi Jim, Mark: according to crash-stats, this crash has jumped up 39 spots and is top ranked at #6 right now. Could you please help find an owner who can investigate? Thanks!
status-firefox47: --- → affected
tracking-e10s: - → ?
Flags: needinfo?(standard8)
Flags: needinfo?(jmathies)

Comment 6

2 years ago
(In reply to Ritu Kothari (:ritu) from comment #5)
> Hi Jim, Mark: according to crash-stats, this crash has jumped up 39 spots
> and is top ranked at #6 right now. Could you please help find an owner who
> can investigate? Thanks!

I think you might be seeing remnants of the build 1 apz crasher which can show up under random signatures.

Neither of the signatures listed here show up in build 2. Please let me know if I'm looking for the wrong thing.

https://crash-stats.mozilla.com/report/list?signature=mozalloc_abort%20%7C%20NS_DebugBreak%20%7C%20mozilla%3A%3Adom%3A%3APBrowser%3A%3ATransition
tracking-e10s: ? → -
Flags: needinfo?(standard8)
Flags: needinfo?(rkothari)
Flags: needinfo?(jmathies)

Comment 7

2 years ago
(In reply to Jim Mathies [:jimm] from comment #6)
> I think you might be seeing remnants of the build 1 apz crasher which can
> show up under random signatures.
> 
> Neither of the signatures listed here show up in build 2. Please let me know
> if I'm looking for the wrong thing.

Your assessment makes sense. Thanks!
Flags: needinfo?(rkothari)
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.