Closed
Bug 1286775
Opened 9 years ago
Closed 8 years ago
Crash in [@ shutdownhang | libpthread-2.19.so@0xc250 ]
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: cristian.lorenzetto, Unassigned)
References
Details
(Keywords: crash, hang, Whiteboard: gfx-noted)
Crash Data
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36
Steps to reproduce:
it is probably a concurrent synchronization problem or a memory leak.
crash code is bp-bdda6a7a-c8a4-4521-96d9-aaf262160712
12/07/2016 19:27
it is caused using MSE. Using seeking function foward and back many times .... before video show corrupted images and then crashs
Updated•9 years ago
|
Crash Signature: [@ shutdownhang | libpthread-2.19.so@0xc250 ]
Component: Untriaged → Audio/Video: Playback
Keywords: crash,
crashreportid
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64
Summary: aarwtet → Crash in [@ shutdownhang | libpthread-2.19.so@0xc250 ]
Comment 1•9 years ago
|
||
thread 0:
0 libpthread-2.19.so@0xc250
1 libnspr4.so PR_WaitCondVar nsprpub/pr/src/pthreads/ptsynch.c:396
2 libxul.so nsEventQueue::GetEvent xpcom/glue/CondVar.h:79
3 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.h:128
4 libxul.so NS_ProcessNextEvent xpcom/glue/nsThreadUtils.cpp:290
5 libxul.so mozilla::layers::CompositorBridgeParent::ShutDown gfx/layers/ipc/CompositorBridgeParent.cpp:649
6 libxul.so mozilla::ShutdownXPCOM xpcom/build/XPCOMInit.cpp:872
7 libxul.so ScopedXPCOMStartup::~ScopedXPCOMStartup toolkit/xre/nsAppRunner.cpp:1472
8 libxul.so mozilla::DefaultDelete<ScopedXPCOMStartup>::operator() mfbt/UniquePtr.h:528
9 libxul.so XREMain::XRE_main mfbt/UniquePtr.h:343
10 libxul.so XRE_main toolkit/xre/nsAppRunner.cpp:4559
11 firefox do_main browser/app/nsBrowserApp.cpp:220
12 firefox main
It looks like something about gfx/layer.
Component: Audio/Video: Playback → Graphics: Layers
Based on recent data it does not look like this is affecting current Firefox versions but is affecting current Thunderbird versions.
Product:
74% Thunderbird vs 26% Firefox
Firefox Versions (current versions appear unaffected):
33% Firefox 39.0
22% Firefox 38.0
11% Firefox 37.0
11% Firefox 44.0
11% Firefox 47.0
11% Firefox 48.0
Thunderbird Versions:
81% Thunderbird 45.*
19% Thunderbird 35.*
Looking at the stacks it appears this is a very different issue with Thunderbird than it is in Firefox. Since there are no reports in current Firefox versions I'm inclined to call this RESOLVED INCOMPLETE (unless someone can reproduce this in a current version). The Thunderbird crashes probably deserve their own bug report.
Keywords: crashreportid
Whiteboard: gfx-noted
As an example:
bp-bdda6a7a-c8a4-4521-96d9-aaf262160712 (Firefox) vs bp-87c39664-d6ef-442a-adfb-5f4922160926 (Thunderbird)
The crashing thread stacks are the same but thread-0 is drastically different. Firefox seems to come from Graphics [mozilla::layers::CompositorBridgeParent::ShutDown] while Thunderbird seems to come from Networking [nsSyncStreamListener::WaitForData()].
Comment 4•8 years ago
|
||
I agree. (Although at this time not worth opening a thunderbird bug report - unless a user has a reproducible case)
Severity: normal → critical
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•