Closed
Bug 824293
Opened 12 years ago
Closed 12 years ago
crash in mozilla::hal_impl::SwitchEventRunnable::Run
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-basecamp:+)
RESOLVED
DUPLICATE
of bug 823203
blocking-basecamp | + |
People
(Reporter: m1, Unassigned)
Details
Seen multiple times during stability test:
Crash reason: SIGSEGV
Crash address: 0x0
Thread 0 (crashed)
0 0x0
r4 = 0x00000004 r5 = 0x44c7ca98 r6 = 0x482984d8 r7 = 0x00000005
r8 = 0xbee2284f r9 = 0x40407c0c r10 = 0x00000000 fp = 0x00000000
sp = 0xbee227e8 lr = 0x41113bf1 pc = 0x00000000
Found by: given as instruction pointer in context
1 libxul.so!mozilla::hal_impl::SwitchEventRunnable::Run [GonkSwitch.cpp : 222 + 0x3]
sp = 0xbee22800 pc = 0x41118a29
Found by: stack scanning
2 libxul.so!nsThread::ProcessNextEvent [nsThread.cpp : 620 + 0x5]
r4 = 0x40407be0 sp = 0xbee22808 pc = 0x4116ec9b
Found by: call frame info
3 libxul.so!NS_ProcessNextEvent_P [nsThreadUtils.cpp : 220 + 0xb]
r4 = 0x00000001 r5 = 0x404330c0 r6 = 0x404024d0 r7 = 0x00000000
r8 = 0x00000000 r9 = 0x40429000 sp = 0xbee22848 pc = 0x4114f0b7
Found by: call frame info
4 libxul.so!mozilla::ipc::MessagePump::Run [MessagePump.cpp : 117 + 0x7]
r4 = 0x404024c0 r5 = 0x404330c0 r6 = 0x404024d0 r7 = 0x00000000
r8 = 0x00000000 r9 = 0x40429000 sp = 0xbee22858 pc = 0x41086d7b
Found by: call frame info
5 libxul.so!MessageLoop::RunInternal [message_loop.cc : 215 + 0x5]
r4 = 0x404330c0 r5 = 0x43949640 r6 = 0x40407be0 r7 = 0xbee22afd
r8 = 0x00000000 r9 = 0x40429000 sp = 0xbee22880 pc = 0x41190409
Found by: call frame info
6 libxul.so!MessageLoop::Run [message_loop.cc : 208 + 0x5]
r4 = 0x404330c0 r5 = 0x43949640 r6 = 0x40407be0 r7 = 0xbee22afd
r8 = 0x00000000 r9 = 0x40429000 sp = 0xbee22888 pc = 0x411904bf
Found by: call frame info
7 libxul.so!nsBaseAppShell::Run [nsBaseAppShell.cpp : 163 + 0x7]
r4 = 0x00000000 r5 = 0x43949640 r6 = 0x40407be0 r7 = 0xbee22afd
r8 = 0x00000000 r9 = 0x40429000 sp = 0xbee228a0 pc = 0x4100f751
Found by: call frame info
8 libxul.so!nsAppStartup::Run [nsAppStartup.cpp : 290 + 0x5]
r4 = 0x4395cc70 r5 = 0x41159a09 r6 = 0x00000000 r7 = 0xbee22afd
r8 = 0x00000000 r9 = 0x40429000 sp = 0xbee228b0 pc = 0x40f733c9
Found by: call frame info
9 libxul.so!XREMain::XRE_mainRun [nsAppRunner.cpp : 3794 + 0x5]
r4 = 0xbee22a0c r5 = 0x41159a09 r6 = 0x00000000 r7 = 0xbee22afd
r8 = 0x00000000 r9 = 0x40429000 sp = 0xbee228b8 pc = 0x409afcbb
Found by: call frame info
10 libxul.so!XREMain::XRE_main [nsAppRunner.cpp : 3860 + 0x5]
r4 = 0xbee22a0c r5 = 0xbee229e7 r6 = 0x00000000 r7 = 0xbee24bf4
r8 = 0x40424000 r9 = 0x40429000 r10 = 0x00000000 fp = 0x00000000
sp = 0xbee229e0 pc = 0x409b2459
Found by: call frame info
11 libxul.so!XRE_main [nsAppRunner.cpp : 3935 + 0x3]
r4 = 0x0001f180 r5 = 0xbee24bf4 r6 = 0x00000001 r7 = 0x00000000
r8 = 0xbee22a0c r9 = 0x00000000 r10 = 0x00000000 fp = 0x00000000
sp = 0xbee22a08 pc = 0x409b25a5
Found by: call frame info
12 b2g!main [nsBrowserApp.cpp : 164 + 0xf]
r4 = 0x409b2559 r5 = 0x00000000 r6 = 0x00000001 r7 = 0xbee24bf4
r8 = 0x00000000 r9 = 0x00000000 r10 = 0x00000000 fp = 0x00000000
sp = 0xbee22b18 pc = 0x0000a11f
Found by: call frame info
13 libc.so!__libc_init [libc_init_dynamic.c : 114 + 0x7]
r4 = 0x00009ec4 r5 = 0xbee24bf4 r6 = 0x00000001 r7 = 0xbee24bfc
r8 = 0x00000000 r9 = 0x00000000 r10 = 0x00000000 fp = 0x00000000
sp = 0xbee24bd8 pc = 0x4011da77
Found by: call frame info
14 libc.so!__cxa_atexit [atexit.c : 99 + 0x3]
r4 = 0x00000000 r5 = 0x00000000 r6 = 0x00000000 r7 = 0x00000000
r8 = 0x00000000 r9 = 0x00000000 r10 = 0x00000000 fp = 0x00000000
sp = 0xbee24bf0 pc = 0x40126437
Found by: call frame info
15 0xbee24db3
r4 = 0x00000000 r5 = 0xbee24d03 r6 = 0xbee24d15 r7 = 0xbee24d28
r8 = 0xbee24d4b r9 = 0xbee24d64 r10 = 0xbee24d81 fp = 0x00000000
sp = 0xbee24c18 pc = 0xbee24db5
Found by: call frame info
Comment 1•12 years ago
|
||
It seems to be similar with bug 823203.
Reporter | ||
Comment 2•12 years ago
|
||
Looks close, I agree. In this case no headphones where inserted or removed but maybe a different symptom of the same bug.
How confident are you this is same same Macro? I'm happy to mark this a dup, and reopen it if it occurs again with the fix for bug 823203.
Comment 3•12 years ago
|
||
(In reply to Michael Vines [:m1] from comment #2)
> Looks close, I agree. In this case no headphones where inserted or removed
> but maybe a different symptom of the same bug.
>
> How confident are you this is same same Macro? I'm happy to mark this a
> dup, and reopen it if it occurs again with the fix for bug 823203.
Could you provide the reproducing steps?
I can help to verify with the fixed patch from bug 823203.
Thanks.
Reporter | ||
Comment 4•12 years ago
|
||
Duping this bug for now, lets see if it comes back once the fix from bug 823203 lands
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•12 years ago
|
blocking-basecamp: ? → +
You need to log in
before you can comment on or make changes to this bug.
Description
•