Closed Bug 625090 Opened 15 years ago Closed 14 years ago

Fennec crash [@ nsDocShellTreeOwner::AddChromeListeners ]

Categories

(Core Graveyard :: Embedding: APIs, defect)

ARM
Android
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: scoobidiver, Unassigned)

Details

(Keywords: crash, Whiteboard: [mobile-crash])

Crash Data

It is #36 top crasher in Fennec 4.0b3 for the last week. Signature nsDocShellTreeOwner::AddChromeListeners UUID 0192da6e-1e03-4317-a168-43dae2110111 Time 2011-01-11 04:47:22.879588 Uptime 0 Install Age 1409729 seconds (2.3 weeks) since version was first installed. Product Fennec Version 4.0b3 Build ID 20101221205132 Branch 1.9 OS Linux OS Version 0.0.0 Linux 2.6.32.9-g68eeef5 #1 PREEMPT Tue Aug 10 16:07:07 PDT 2010 armv7l CPU arm Crash Reason SIGSEGV Crash Address 0x0 Frame Module Signature [Expand] Source 0 libxul.so nsDocShellTreeOwner::AddChromeListeners embedding/browser/webBrowser/nsDocShellTreeOwner.cpp:886 1 libxul.so nsDocShellTreeOwner::OnProgressChange embedding/browser/webBrowser/nsDocShellTreeOwner.cpp:722 2 libxul.so nsDocLoader::FireOnProgressChange uriloader/base/nsDocLoader.cpp:1241 3 libxul.so nsDocLoader::OnProgress uriloader/base/nsDocLoader.cpp:1143 4 libxul.so mozilla::net::HttpChannelChild::OnProgress netwerk/protocol/http/HttpChannelChild.cpp:458 5 libxul.so mozilla::net::HttpChannelChild::RecvOnProgress netwerk/protocol/http/HttpChannelChild.cpp:429 6 libxul.so mozilla::net::PHttpChannelChild::OnMessageReceived PHttpChannelChild.cpp:522 7 libxul.so mozilla::dom::PContentChild::OnMessageReceived PContentChild.cpp:949 8 libxul.so mozilla::ipc::AsyncChannel::OnDispatchMessage ipc/glue/AsyncChannel.cpp:262 9 libxul.so mozilla::ipc::RPCChannel::OnMaybeDequeueOne ipc/glue/RPCChannel.cpp:440 10 libxul.so RunnableMethod<mozilla::ipc::RPCChannel, bool , Tuple0>::Run ipc/chromium/src/base/task.h:308 11 libxul.so mozilla::ipc::RPCChannel::DequeueTask::Run RPCChannel.h:475 12 libxul.so MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:344 13 libxul.so MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:354 14 libxul.so MessageLoop::DoWork ipc/chromium/src/base/message_loop.cc:451 15 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:115 16 libxul.so mozilla::ipc::MessagePumpForChildProcess::Run ipc/glue/MessagePump.cpp:230 17 libxul.so MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:220 18 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:512 19 libxul.so nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:198 20 libxul.so XRE_RunAppShell toolkit/xre/nsEmbedFunctions.cpp:631 21 libxul.so mozilla::ipc::MessagePumpForChildProcess::Run ipc/glue/MessagePump.cpp:222 22 libxul.so MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:220 23 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:512 24 libxul.so XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:510 25 libmozutils.so ChildProcessInit other-licenses/android/APKOpen.cpp:691 26 plugin-container main ipc/app/MozillaRuntimeMainAndroid.cpp:69 27 libc.so libc.so@0xd3c2 More reports at: http://crash-stats.mozilla.com/report/list?range_value=4&range_unit=weeks&signature=nsDocShellTreeOwner%3A%3AAddChromeListeners
Olli, this looks like a similar situation as bug 561457, which was never fully explained. I'm leery of just applying the same bandaid fix, though, as I don't know what would happen if the chrome listeners aren't added.
So this is also a shutdown crasher? I think we shouldn't care too much what content process is doing at that point. Bandaid would be ok.
This stack doesn't look like a shutdown to me. That's what makes me more worried this time.
Crash Signature: [@ nsDocShellTreeOwner::AddChromeListeners ]
Whiteboard: [mobile-crash]
The last crash happened in the Fennec emulator 4.0.1 (see bug 669413 for the reason). I close it as WFM.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.