Closed
Bug 888675
Opened 12 years ago
Closed 12 years ago
crash in std::deque<MessageLoop::PendingTask, std::allocator<MessageLoop::PendingTask> >::operator= @ libEGL
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox22 | --- | affected |
| firefox23 | --- | affected |
| firefox24 | --- | unaffected |
People
(Reporter: scoobidiver, Unassigned)
Details
(Keywords: crash, topcrash, Whiteboard: [native-crash])
Crash Data
It's #784 crasher in 22.0 and #21 in 23.0b1.
Signature std::deque<MessageLoop::PendingTask, std::allocator<MessageLoop::PendingTask> >::operator=(std::deque<MessageLoop::PendingTask, std::allocator<MessageLoop::PendingTask> > const&) More Reports Search
UUID 11ee7dfb-5960-474c-821d-c1d722130629
Date Processed 2013-06-29 08:31:41.925854
Uptime 71
Last Crash 55958 seconds before submission
Install Age 103414 since version was first installed.
Install Time 2013-06-28 03:47:27
Product FennecAndroid
Version 23.0
Build ID 20130625123817
Release Channel beta
OS Android
OS Version 0.0.0 Linux 3.0.31-1090526 #1 SMP PREEMPT Wed Mar 27 16:11:17 KST 2013 armv7l samsung/t0ltespr/t0lte
Build Architecture arm
Build Architecture Info ARMv0 | None
Crash Reason SIGSEGV
Crash Address 0x130004
User Comments watching youtube
App Notes
AdapterDescription: 'ARM -- Mali-400 MP -- OpenGL ES 2.0 -- Model: SPH-L900, Product: t0ltespr, Manufacturer: samsung, Hardware: smdk4x12'
GL Layers! EGL? EGL+ GL Context? GL Context+ GL Layers+
samsung SPH-L900
samsung/t0ltespr/t0ltespr:4.1.2/JZO54K/L900VPAMC2:user/release-keys
Android Version 16 (REL)
Frame Module Signature Source
0 libEGL.so libEGL.so@0xabf4
1 libEGL.so libEGL.so@0xa9eb
2 libEGL.so libEGL.so@0x2212a
3 libEGL.so libEGL.so@0x22106
4 libEGL.so libEGL.so@0xc995
5 libxul.so std::deque<MessageLoop::PendingTask, std::allocator<MessageLoop::PendingTask> >::operator=(std::deque<MessageLoop::PendingTask, std::allocator<MessageLoop::PendingTask> > const&) /tools/android-ndk-r8c/sources/cxx-stl/stlport/stlport/stl/_deque.h
6 libxul.so libxul.so@0x11be69c
7 libxul.so RunnableMethod<IPC::ChannelProxy::Context, void (IPC::ChannelProxy::Context::*)(), Tuple0>::Run() ipc/chromium/src/base/tuple.h
8 libxul.so mozilla::ipc::RPCChannel::DequeueTask::Run() obj-firefox/dist/include/mozilla/ipc/RPCChannel.h
9 libxul.so MessageLoop::RunTask(Task*) ipc/chromium/src/base/message_loop.cc
10 libxul.so MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask const&) ipc/chromium/src/base/message_loop.cc
11 libxul.so MessageLoop::DoWork() ipc/chromium/src/base/message_loop.cc
12 libxul.so base::MessagePumpDefault::Run(base::MessagePump::Delegate*) ipc/chromium/src/base/message_pump_default.cc
13 libxul.so MessageLoop::RunInternal() ipc/chromium/src/base/message_loop.cc
14 libxul.so MessageLoop::Run() ipc/chromium/src/base/message_loop.cc
15 libxul.so base::Thread::ThreadMain() ipc/chromium/src/base/thread.cc
16 libxul.so ThreadFunc ipc/chromium/src/base/platform_thread_posix.cc
17 libc.so libc.so@0x12e02
18 libc.so libc.so@0x1255a
19 libEGL.so libEGL.so@0x22c3a
More reports at:
https://crash-stats.mozilla.com/report/list?product=FennecAndroid&signature=std%3A%3Adeque%3CMessageLoop%3A%3APendingTask%2C+std%3A%3Aallocator%3CMessageLoop%3A%3APendingTask%3E+%3E%3A%3Aoperator%3D%28std%3A%3Adeque%3CMessageLoop%3A%3APendingTask%2C+std%3A%3Aallocator%3CMessageLoop%3A%3APendingTask%3E+%3E+const%26%29
| Reporter | ||
Comment 1•12 years ago
|
||
It's now #13 in 23.0b1 and #8 in the first hours of 23.0b2.
| Reporter | ||
Comment 2•12 years ago
|
||
It's finally #10 crasher in 23.0b2 so a top crasher according to https://wiki.mozilla.org/CrashKill/Topcrash.
There are no crashes in 24.0a2 and 25.0a1 because it's fixed. Indeed, there were crashes in 23.0a1 and 24.0a1 up to 24.0a1/20130603.
status-firefox24:
--- → unaffected
Keywords: topcrash
| Reporter | ||
Comment 3•12 years ago
|
||
I confirm that Firefox 24.0b1 is not affected.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•