Closed Bug 736526 Opened 10 years ago Closed 6 years ago

OOM crash in nsFontMetrics::Init


(Core :: Graphics, defect)

14 Branch
Not set





(Reporter: scoobidiver, Unassigned)



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

Crash Data

It first appeared in 14.0a1/20120314130626. The regression range is:

Signature 	TouchBadMemory More Reports Search
UUID	2b0d2d78-158d-40bd-a6ec-c22d42120315
Date Processed	2012-03-15 01:52:21
Uptime	3
Last Crash	3.5 hours before submission
Install Age	3.7 hours since version was first installed.
Install Time	2012-03-14 22:11:58
Product	FennecAndroid
Version	14.0a1
Build ID	20120314130626
Release Channel	nightly
OS	Linux
OS Version	0.0.0 Linux #1 SMP PREEMPT Fri Jan 6 20:17:17 CST 2012 armv7l
Build Architecture	arm
Build Architecture Info	
Crash Reason	SIGSEGV
Crash Address	0x0
App Notes 	
EGL? EGL+ AdapterVendorID: mapphone_cdma, AdapterDeviceID: DROID BIONIC.
AdapterDescription: 'Android, Model: 'DROID BIONIC', Product: 'targa_vzw', Manufacturer: 'motorola', Hardware: 'mapphone_cdma''.
GL Context? GL Context+ GL Layers? GL Layers- 
Processor Notes 	This dump is too long and has triggered the automatic truncation routine
EMCheckCompatibility	True
OOMAllocationSize	112

Frame 	Module 	Signature 	Source
0 	TouchBadMemory 	memory/mozalloc/mozalloc_abort.cpp:68
1 	mozalloc_abort 	memory/mozalloc/mozalloc_abort.cpp:89
2 	moz_xmalloc 	memory/mozalloc/mozalloc.cpp:105
3 	gfxAndroidPlatform::CreateFontGroup 	mozalloc.h:229
4 	nsFontMetrics::Init 	gfx/src/nsFontMetrics.cpp:141
5 	nsFontCache::GetMetricsFor 	gfx/src/nsDeviceContext.cpp:174
6 	nsDeviceContext::GetMetricsFor 	gfx/src/nsDeviceContext.cpp:289
7 	nsLayoutUtils::GetFontMetricsForStyleContext 	layout/base/nsLayoutUtils.cpp:2114
8 	nsLayoutUtils::GetFontMetricsForFrame 	layout/base/nsLayoutUtils.cpp:2094
9 	GetFontGroupForFrame 	layout/generic/nsTextFrameThebes.cpp:1641
10 	BuildTextRunsScanner::BuildTextRunForFrames 	layout/generic/nsTextFrameThebes.cpp:1877
11 	BuildTextRunsScanner::FlushFrames 	layout/generic/nsTextFrameThebes.cpp:1397
12 	BuildTextRunsScanner::ScanFrame 	layout/generic/nsTextFrameThebes.cpp:1560
13 	BuildTextRunsScanner::ScanFrame 	layout/generic/nsTextFrameThebes.cpp:1600
14 	BuildTextRunsScanner::ScanFrame 	layout/generic/nsTextFrameThebes.cpp:1600
15 	BuildTextRunsScanner::ScanFrame 	layout/generic/nsTextFrameThebes.cpp:1600
16 	nsTextFrame::EnsureTextRun 	layout/generic/nsTextFrameThebes.cpp:1300
17 	nsTextFrame::AddInlineMinWidthForFlow 	layout/generic/nsTextFrameThebes.cpp:6580
18 	nsTextFrame::AddInlineMinWidth 	layout/generic/nsTextFrameThebes.cpp:6728
19 	nsBlockFrame::GetMinWidth 	layout/generic/nsBlockFrame.cpp:759
20 	nsLayoutUtils::IntrinsicForContainer 	layout/base/nsLayoutUtils.cpp:2464
21 	nsTableCellFrame::GetMinWidth 	layout/tables/nsTableCellFrame.cpp:736
22 	GetWidthInfo 	layout/tables/BasicTableLayoutStrategy.cpp:120
23 	BasicTableLayoutStrategy::ComputeColumnIntrinsicWidths 	layout/tables/BasicTableLayoutStrategy.cpp:245
24 	BasicTableLayoutStrategy::ComputeIntrinsicWidths 	layout/tables/BasicTableLayoutStrategy.cpp:425
25 	BasicTableLayoutStrategy::GetMinWidth 	layout/tables/BasicTableLayoutStrategy.cpp:75

More reports at:
More reports at:
Blocks: 719373
Crash Signature: [@ TouchBadMemory] → [@ TouchBadMemory] [@ TouchBadMemory | mozalloc_abort | moz_xmalloc | gfxAndroidPlatform::CreateFontGroup]
Crash Signature: [@ TouchBadMemory] [@ TouchBadMemory | mozalloc_abort | moz_xmalloc | gfxAndroidPlatform::CreateFontGroup] → [@ TouchBadMemory] [@ TouchBadMemory | mozalloc_abort | moz_xmalloc | gfxAndroidPlatform::CreateFontGroup ]
I have experienced this crash lately with Firefor Nightly on Android. I was sharing a page via email and after I got back to the page and tried to navigate away Firefox crashed.

Here the crash report: bp-4a2fd7ba-4477-4d7b-a410-00a612120503

I wasn't able to reproduce it yet.
Summary: crash in nsFontMetrics::Init @ TouchBadMemory → OOM crash in nsFontMetrics::Init
I am closing this bug report as incomplete since there are no reports beyond Fennec 15. Please reopen this bug report if you can reproduce the crash in the current Fennec version.
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.