Closed Bug 750220 Opened 14 years ago Closed 7 years ago

OOM crash in XPCJSStackFrame::CreateStack

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Version:
14 Branch
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
blocking-fennec1.0 --- -

People

(Reporter: scoobidiver, Assigned: dmandelin)

Details

(Keywords: crash, Whiteboard: [native-crash])

Crash Data

Signature TouchBadMemory | mozalloc_abort | moz_xmalloc | NS_Alloc_P More Reports Search UUID 3ba9d4cb-71d7-4498-b3eb-6d7ea2120430 Date Processed 2012-04-30 06:10:55 Uptime 7 Last Crash 2.7 hours before submission Install Age 9.5 hours since version was first installed. Install Time 2012-04-29 20:39:42 Product FennecAndroid Version 14.0a2 Build ID 20120429042006 Release Channel aurora OS Linux OS Version 0.0.0 Linux 2.6.35.10-gd2564fb #1 PREEMPT Thu Jun 9 14:33:05 CST 2011 armv7l Build Architecture arm Build Architecture Info Crash Reason SIGSEGV Crash Address 0x0 App Notes EGL? EGL+ AdapterVendorID: spade, AdapterDeviceID: Desire HD. AdapterDescription: 'Android, Model: 'Desire HD', Product: 'htc_ace', Manufacturer: 'HTC', Hardware: 'spade''. GL Context? GL Context+ GL Layers? GL Layers- HTC Desire HD cingular_us/htc_ace/ace:2.3.3/GRI40/93396:user/release-keys EMCheckCompatibility True OOMAllocationSize 97 Frame Module Signature Source 0 libmozalloc.so TouchBadMemory memory/mozalloc/mozalloc_abort.cpp:68 1 libmozalloc.so mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:89 2 libmozalloc.so moz_xmalloc memory/mozalloc/mozalloc.cpp:89 3 libxul.so NS_Alloc_P xpcom/base/nsMemoryImpl.cpp:195 4 libxul.so nsMemory::Clone obj-firefox/xpcom/build/nsMemory.cpp:61 5 libxul.so XPCJSStackFrame::CreateStack js/xpconnect/src/XPCStack.cpp:153 6 libxul.so XPCJSStack::CreateStack js/xpconnect/src/XPCStack.cpp:89 7 libxul.so nsXPConnect::GetCurrentJSStack js/xpconnect/src/nsXPConnect.cpp:1945 8 libxul.so nsXPCException::NewException js/xpconnect/src/XPCException.cpp:445 9 libxul.so XPCThrower::BuildAndThrowException js/xpconnect/src/XPCThrower.cpp:208 10 libxul.so XPCThrower::ThrowBadResult js/xpconnect/src/XPCThrower.cpp:144 11 libxul.so XPCWrappedNative::CallMethod js/xpconnect/src/XPCInlines.h:693 12 libxul.so XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:1549 13 libxul.so js::Interpret js/src/jscntxtinlines.h:314 14 libxul.so js::RunScript js/src/jsinterp.cpp:475 15 libxul.so js::Invoke js/src/jsinterp.cpp:535 16 libxul.so JS_CallFunctionValue js/src/jsapi.cpp:5416 17 libxul.so nsXPCWrappedJSClass::CallMethod js/xpconnect/src/XPCWrappedJSClass.cpp:1509 18 libxul.so nsXPCWrappedJS::CallMethod js/xpconnect/src/XPCWrappedJS.cpp:617 19 libxul.so PrepareAndDispatch xpcom/reflect/xptcall/src/md/unix/xptcstubs_arm.cpp:138 ... More reports at: https://crash-stats.mozilla.com/report/list?signature=TouchBadMemory+|+mozalloc_abort+|+moz_xmalloc+|+NS_Alloc_P
It's #5 top crasher in 14.0a2.
blocking-fennec1.0: --- → ?
Keywords: topcrash
Naoki, can you get get URLs from these reports?
Keywords: qawanted
URL: about:home about:blank I'll
due to Bug 745695, I cannot get on the server to comb the log via shell script. I cannot seem to access it using VPN. The above was a manual search through crash-stats.
Socorro seems to report the issue as early as FennecNative 14a1 20120331031108: https://crash-stats.mozilla.com/report/index/84149428-90a0-437a-8da7-f09d12120407 Note: Fennec 12 20120403204709: https://crash-stats.mozilla.com/report/index/e43d41e2-bf2b-4e6b-b4db-962282120413 is a different crash but placed in the same signature. Product Version Percentage Number Of Crashes FennecAndroid 14.0a2 57.143 % 32 FennecAndroid 14.0a1 25.000 % 14 FennecAndroid 15.0a1 8.929 % 5 Fennec 12.0b4 7.143 % 4 FennecAndroid 13.0a2 1.786 % 1
Uptime Range Percentage Number Of Crashes < 1 min 85.714 % 48 1-5 min 10.714 % 6 5-15 min 3.571 % 2
(In reply to Naoki Hirata :nhirata from comment #5) > Socorro seems to report the issue as early as FennecNative 14a1 > 20120331031108: > https://crash-stats.mozilla.com/report/index/84149428-90a0-437a-8da7- > f09d12120407 This one is bug 749543 which is less frequent.
Keywords: qawanted
blocking-fennec1.0: ? → +
David, can you get someone to look at this?
Assignee: nobody → dmandelin
(In reply to Brad Lassey [:blassey] from comment #9) > David, can you get someone to look at this? These OOM crashes keep coming up for Fennec but I don't understand what we're supposed to do about them: In this case, as with most of them, some attempted allocation is failing, and so our infallible malloc crashes. There doesn't seem to be much that could be done about it. I suppose in this case, the code is trying to copy a filename string, so you could just make it use an empty string or something (I assume), but if the system is OOM, the next allocation will fail, so we'll just crash right away anyway.
Not blocking because the OOM nature is hard to be actionable. We can renom if other general memory usage fixes don't help the situation, and this problem persists.
blocking-fennec1.0: + → -
It's #28 top crasher in 14.0b1 and #45 in 14.0b2 with other crashes with the same signature. I removed the topcrash keyword.
Keywords: topcrash
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INACTIVE
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Closing because no crash reported since 12 weeks.
Status: REOPENED → RESOLVED
Closed: 8 years ago → 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.