Closed
Bug 739136
Opened 13 years ago
Closed 13 years ago
segfault in B2G on desktop
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 739452
People
(Reporter: djf, Unassigned)
Details
B2G crashes for me tonight on MacOS with the trace below. This looks like it is a different stack trace than https://bugzilla.mozilla.org/show_bug.cgi?id=739123
djf$ hg bisect -b
The first bad revision is:
changeset: 90273:7f87b434f7c6
Thread 3 Crashed: Gecko_IOThread
0 XUL 0x0000000101f19548 mozilla::ipc::RilClient::OpenSocket() + 136 (Ril.cpp:179)
1 XUL 0x0000000101f19801 mozilla::ipc::RilReconnectTask::Run() + 17 (Ril.cpp:123)
2 XUL 0x0000000101f8f823 MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask const&) + 147 (message_loop.cc:319)
3 XUL 0x0000000101f8fa3e MessageLoop::DoDelayedWork(base::Time*) + 302 (message_loop.cc:453)
4 XUL 0x0000000101f99a5f base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 159 (message_pump_libevent.cc:315)
5 XUL 0x0000000101f8f280 MessageLoop::Run() + 64 (message_loop.cc:487)
6 XUL 0x0000000101f94f73 base::Thread::ThreadMain() + 131 (thread.cc:159)
7 XUL 0x0000000101f9a0ea ThreadFunc(void*) + 10 (platform_thread_posix.cc:28)
8 libSystem.B.dylib 0x00007fff8721cfd6 _pthread_start + 331
9 libSystem.B.dylib 0x00007fff8721ce89 thread_start + 13
Summary: segfault in B2G on MacOS → segfault in B2G on desktop
Reporter | ||
Comment 2•13 years ago
|
||
Workaround: Download this python code and run this before starting b2g:
% python fauxphone.py -i &
Code is here: https://gist.github.com/2205561
I'm not sure who wrote that code, but it works for me
Comment 3•13 years ago
|
||
(In reply to David Flanagan from comment #2)
> I'm not sure who wrote that code, but it works for me
fwit, mrbkap wrote that.
Comment 4•13 years ago
|
||
Duplicate of bug 739452 (this one was filed first, but bug 739452 has more information and resolution chain.)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•