Closed Bug 738940 Opened 10 years ago Closed 3 years ago

OOM crash with abort message "ABORT: out of memory: file /builds/slave/m-cen-andrd-ntly/build/layout/style/nsCSSValue.cpp, line 664"

Categories

(Core :: CSS Parsing and Computation, defect)

14 Branch
ARM
Android
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: scoobidiver, Unassigned)

References

Details

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

Crash Data

There are four crashes so far in 14.0a1.

Signature 	TouchBadMemory | mozalloc_abort More Reports Search
UUID	93831c73-163b-42a1-8fbe-cc8aa2120322
Date Processed	2012-03-22 18:47:43
Uptime	19
Last Crash	32 seconds before submission
Install Age	35 seconds since version was first installed.
Install Time	2012-03-22 18:46:25
Product	FennecAndroid
Version	14.0a1
Build ID	20120322031220
Release Channel	nightly
OS	Linux
OS Version	0.0.0 Linux 2.6.35.7-g790a33c #1 SMP PREEMPT Fri Aug 12 22:19:20 CDT 2011 armv7l
Build Architecture	arm
Build Architecture Info	
Crash Reason	SIGSEGV
Crash Address	0x0
App Notes 	
EGL? EGL+ AdapterVendorID: mapphone_cdma, AdapterDeviceID: DROID3.
AdapterDescription: 'Android, Model: 'DROID3', Product: 'solana_vzw', Manufacturer: 'motorola', Hardware: 'mapphone_cdma''.
GL Context? GL Context+ GL Layers? GL Layers-
xpcom_runtime_abort(###!!! ABORT: out of memory: file /builds/slave/m-cen-andrd-ntly/build/layout/style/nsCSSValue.cpp, line 664)
motorola DROID3
verizon/solana_vzw/cdma_solana:2.3.4/5.5.1_84_D3G-66_M2-6/111228:user/release-keys
EMCheckCompatibility	True

Frame 	Module 	Signature [Expand] 	Source
0 	libmozalloc.so 	TouchBadMemory 	memory/mozalloc/mozalloc_abort.cpp:68
1 	libmozalloc.so 	mozalloc_abort 	memory/mozalloc/mozalloc_abort.cpp:89
2 	dalvik-heap (deleted) 	dalvik-heap @0x11f011f 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=TouchBadMemory+|+mozalloc_abort
Zero volume for this signature.  Please file new bugs as appropriate.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.