Closed Bug 636052 Opened 11 years ago Closed 10 years ago

crash [@ txNamedAttributeStep::evaluate]


(Core :: Layout: Tables, defect)

Not set



Tracking Status
fennec - ---


(Reporter: ashah, Unassigned)


(Keywords: crash, qawanted, Whiteboard: [need-str])

Crash Data

This bug was filed from the Socorro interface and is 
report bp-3f703d20-a58c-48e7-ba80-2a7a32110222 .
#2 top crasher for fennec 4.0b6pre last week

Signature	txNamedAttributeStep::evaluate
UUID	3f703d20-a58c-48e7-ba80-2a7a32110222
Time 	2011-02-22 16:23:00.265394
Uptime	91
Install Age	110374 seconds (1.3 days) since version was first installed.
Product	Fennec
Version	4.0b6pre
Build ID	20110221042438
Branch	2.0
OS	Linux
OS Version	0.0.0 Linux #1 Fri Dec 3 01:04:14 KST 2010 armv7l
CPU	arm
CPU Info	
Crash Reason	SIGSEGV
Crash Address	0xbe6d6ff0
User Comments	
Processor Notes 	WARNING: Json file missing Add-ons
EMCheckCompatibility	False

Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	txNamedAttributeStep::evaluate 	nsTArray.h:235
1 		@0x4202f2ff 	
2 	nsTableFrame::~nsTableFrame 	layout/tables/nsTableFrame.cpp:263
3 	nsTableFrame::PlaceRepeatedFooter 	layout/tables/nsTableFrame.cpp:2653
4 	nsTableFrame::GetFrameAtOrBefore 	layout/generic/nsIFrame.h:1040
fennec crash: flagging for triage
tracking-fennec: --- → ?
5 crashes since yesterday. Alex, can you investigate?
Assignee: nobody → alexp
Whiteboard: [need-str]
tracking-fennec: ? → 2.0+
Cannot get this crash.
Any clue how to reproduce it?
Component: General → Layout
OS: Linux → Android
Product: Fennec → Core
QA Contact: general → layout
Hardware: All → ARM
Component: Layout → Layout: Tables
QA Contact: layout → layout.tables
That stack is completely bogus.  Those functions don't call each other.
The bad stacks are filed as bug 637243.
no crashes with this stack since the 23rd. As has been pointed out, the stack is bogus, unblocking.
tracking-fennec: 2.0+ → 2.0-
Assignee: alexp → nobody
Keywords: qawanted
Crash Signature: [@ txNamedAttributeStep::evaluate]
there is no stack with this anymore
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.