Closed
Bug 612011
Opened 14 years ago
Closed 10 years ago
Crash [@ nanojit::Assembler::findRegFor2 ] on Android arm v6 devices
Categories
(Core Graveyard :: Nanojit, defect)
Tracking
(fennec-)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
fennec | - | --- |
People
(Reporter: mwu, Unassigned)
Details
(Keywords: crash)
Crash Data
This appears to be the current top crash since we got crash reporting working again. http://crash-stats.mozilla.com/report/list?product=Fennec&version=Fennec%3A4.0b3pre&query_search=signature&query_type=exact&query=&date=11%2F13%2F2010%2011%3A02%3A40&range_value=2&range_unit=days&hang_type=any&process_type=any&plugin_field=&plugin_query_type=&plugin_query=&do_query=1&admin=&signature=nanojit%3A%3AAssembler%3A%3AfindRegFor2 http://crash-stats.mozilla.com/report/index/2f0e2510-d559-4ce9-86db-716ec2101112
Updated•14 years ago
|
Severity: normal → critical
Comment 1•14 years ago
|
||
It is #2 top crasher in Fennec 4.0b3pre for the last week.
tracking-fennec: --- → ?
Keywords: topcrash
Updated•14 years ago
|
Assignee: general → nobody
Component: JavaScript Engine → Nanojit
QA Contact: general → nanojit
Updated•14 years ago
|
tracking-fennec: ? → 2.0-
Comment 2•14 years ago
|
||
It is now #1 top crasher in Fennec 4.0b3pre for the last week. Signature nanojit::Assembler::findRegFor2 UUID 03805237-ac38-4cc4-9931-c5fd92101209 Time 2010-12-09 22:55:26.382358 Uptime 35 Install Age 202 seconds (3.4 minutes) since version was first installed. Product Fennec Version 4.0b3pre Build ID 20101209041929 Branch 2.0 OS Linux OS Version 0.0.0 Linux 2.6.32.9-perf #1 PREEMPT Sat Sep 11 12:44:11 CST 2010 armv6l CPU arm CPU Info Crash Reason SIGSEGV Crash Address 0x0 User Comments App Notes nothumb Build HUAWEI Ideos Huawei/U8150/U8150/U8150:2.2/FRF91/eng.huawei.20100911.122209:user/release-keys Frame Module Signature [Expand] Source 0 libxul.so nanojit::Assembler::findRegFor2 js/src/nanojit/LIR.h:780 1 libxul.so nanojit::Assembler::asm_cmpd js/src/nanojit/NativeARM.cpp:2280 2 libxul.so nanojit::Assembler::asm_branch js/src/nanojit/NativeARM.cpp:2380 3 libxul.so nanojit::Assembler::gen js/src/nanojit/Assembler.cpp:1406 4 libxul.so nanojit::Assembler::compile js/src/nanojit/Assembler.cpp:1084 5 libxul.so js::TraceRecorder::compile js/src/jstracer.cpp:4452 6 libxul.so js::TraceRecorder::endLoop js/src/jstracer.cpp:5052 7 libxul.so js::TraceRecorder::monitorRecording js/src/jsopcode.tbl:483 8 libxul.so js::Interpret js/src/jsinterp.cpp:2670 9 libxul.so js::Invoke js/src/jsinterp.cpp:657 10 libxul.so js::ExternalInvoke js/src/jsinterp.cpp:858 11 libxul.so JS_CallFunctionValue js/src/jsinterp.h:962 12 libxul.so nsFrameMessageManager::ReceiveMessage content/base/src/nsFrameMessageManager.cpp:473 13 libxul.so nsAsyncMessageToChild::Run content/base/src/nsFrameLoader.cpp:1828 14 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:626 15 libxul.so NS_ProcessNextEvent_P nsThreadUtils.cpp:250 16 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:110 17 libxul.so MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:219 18 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:202 19 libxul.so nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:192 20 libxul.so nsAppStartup::Run toolkit/components/startup/src/nsAppStartup.cpp:191 21 libxul.so XRE_main toolkit/xre/nsAppRunner.cpp:3691 22 libxul.so GeckoStart toolkit/xre/nsAndroidStartup.cpp:131 23 libc.so libc.so@0x1103f 24 libc.so libc.so@0x10b23 More reports at: http://crash-stats.mozilla.com/report/list?range_value=4&range_unit=weeks&signature=nanojit%3A%3AAssembler%3A%3AfindRegFor2&version=Fennec%3A4.0b3pre
Comment 3•14 years ago
|
||
See bug 612099 comment 6 and onwards -- supposedly ARMv6 devices aren't supported, and therefore this shouldn't be a blocker.
Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ nanojit::Assembler::findRegFor2 ]
Comment 4•13 years ago
|
||
Nick, is this still a bug. I see related signatures but in very low volume. Are the nanojit bugs even valid. Wasn't this part of the tracer that was removed?
Comment 5•13 years ago
|
||
You're right, Nanojit was removed from Mozilla code along with the tracer, so this doesn't affect Mozilla any more. It might still affect Adobe (they still use Nanojit) so let's keep it open.
Comment 7•10 years ago
|
||
Nanojit is long gone.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•