Closed Bug 634457 Opened 11 years ago Closed 10 years ago

crash [@ mozilla::DOMSVGPathSegList::Initialize]

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
critical

Tracking

(fennec-)

RESOLVED WORKSFORME
Tracking Status
fennec - ---

People

(Reporter: ashah, Unassigned)

Details

(Keywords: crash, Whiteboard: [invalid-wfm])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-c0edce77-47aa-49c3-bb1e-61c4f2110208 .
============================================================= 
#1 crasher for fennec 4.0b5pre in last week

Signature	mozilla::DOMSVGPathSegList::Initialize
UUID	c0edce77-47aa-49c3-bb1e-61c4f2110208
Time 	2011-02-08 23:56:08.461017
Uptime	490
Install Age	530 seconds (8.8 minutes) since version was first installed.
Product	Fennec
Version	4.0b5pre
Build ID	20110208042420
Branch	2.0
OS	Linux
OS Version	0.0.0 Linux 2.6.32.17-cyanogenmod #25 PREEMPT Wed Jan 26 20:41:43 EST 2011 armv7l
CPU	arm
CPU Info	
Crash Reason	SIGSEGV
Crash Address	0xffffffff
User Comments	
Processor Notes 	
EMCheckCompatibility	False


Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	libxul.so 	mozilla::DOMSVGPathSegList::Initialize 	nsCOMPtr.h:443
similar to Bug 626051 ?
tracking-fennec: --- → ?
I think the crash stack is bogus, and suspect this is further problems from cyanogen nightlies, as every weird-looking crash in 4.0b5 seems to have a cyanogenmod signature.
tracking-fennec: ? → 2.0-
Crash Signature: [@ mozilla::DOMSVGPathSegList::Initialize]
Whiteboard: [invalid-wfm]
There have been no crashes for the last four weeks.
I close it as WFM.
Status: NEW → RESOLVED
Closed: 10 years ago
OS: Linux → Android
Hardware: All → ARM
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.