Closed Bug 806071 Opened 10 years ago Closed 4 years ago

crash in js::analyze::ScriptAnalysis::analyzeLifetimes mainly with AMD Radeon HD 6250/6290/6310/6320/6400M (Wrestler/Vancouver Asics)


(Core :: JavaScript Engine, defect)

19 Branch
Windows XP
Not set



Tracking Status
firefox17 - ---
firefox19 + affected
firefox20 - affected
firefox21 --- affected
firefox22 --- affected


(Reporter: scoobidiver, Unassigned)



(Keywords: crash)

Crash Data

It's similar to bug 723458.
It's #180 top browser crasher in 16.0.1, #249 in 18.0a2 and #373 in 19.0a1 but #26 in 17.0b3.

I've checked 17.0 correlations of the last four days and it's not correlated to a specific extension or DLL.

Signature 	js::analyze::ScriptAnalysis::analyzeLifetimes(JSContext*) More Reports Search
UUID	866b21cb-bd11-4884-8602-bee6e2121026
Date Processed	2012-10-26 20:08:35
Uptime	950
Last Crash	21.7 hours before submission
Install Age	15.8 minutes since version was first installed.
Install Time	2012-10-26 19:52:29
Product	Firefox
Version	19.0a1
Build ID	20121026030606
Release Channel	nightly
OS	Windows NT
OS Version	6.1.7601 Service Pack 1
Build Architecture	x86
Build Architecture Info	GenuineIntel family 6 model 37 stepping 5
Crash Address	0x4001
App Notes 	
AdapterVendorID: 0x8086, AdapterDeviceID: 0x0046, AdapterSubsysID: 00468086, AdapterDriverVersion:
D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+ 
EMCheckCompatibility	True
Adapter Vendor ID	0x8086
Adapter Device ID	0x0046
Total Virtual Memory	2147352576
Available Virtual Memory	1551204352
System Memory Use Percentage	42
Available Page File	3082817536
Available Physical Memory	1239859200

Frame 	Module 	Signature 	Source
0 	mozjs.dll 	js::analyze::ScriptAnalysis::analyzeLifetimes 	js/src/jsanalyze.cpp:721
1 	mozjs.dll 	js::analyze::ScriptAnalysis::analyzeSSA 	js/src/jsanalyze.cpp:1207
2 	mozjs.dll 	js::analyze::ScriptAnalysis::analyzeTypes 	js/src/jsinfer.cpp:4409
3 	mozjs.dll 	JSScript::ensureRanInference 	js/src/jsinferinlines.h:1712
4 	mozjs.dll 	js::types::AutoEnterCompilation::init 	js/src/jsinferinlines.h:429
5 	mozjs.dll 	js::mjit::Compiler::performCompilation 	js/src/methodjit/Compiler.cpp:546
6 	mozjs.dll 	js::mjit::Compiler::compile 	js/src/methodjit/Compiler.cpp:140
7 	mozjs.dll 	js::mjit::CanMethodJIT 	js/src/methodjit/Compiler.cpp:1095
8 	mozjs.dll 	js::Interpret 	js/src/jsinterp.cpp:1390
9 	mozjs.dll 	js::RunScript 	js/src/jsinterp.cpp:316
10 	mozjs.dll 	js::InvokeKernel 	js/src/jsinterp.cpp:379
11 	mozjs.dll 	js::Invoke 	js/src/jsinterp.h:109
12 	mozjs.dll 	js::CallOrConstructBoundFunction 	js/src/jsfun.cpp:1103
13 	mozjs.dll 	js::InvokeKernel 	js/src/jsinterp.cpp:367
14 	mozjs.dll 	js::Invoke 	js/src/jsinterp.cpp:412
15 	mozjs.dll 	JS_CallFunctionValue 	js/src/jsapi.cpp:5890
16 	xul.dll 	nsJSContext::CallEventHandler 	dom/base/nsJSEnvironment.cpp:1913
17 	xul.dll 	nsGlobalWindow::RunTimeoutHandler 	dom/base/nsGlobalWindow.cpp:9751
18 	xul.dll 	nsGlobalWindow::RunTimeout 	dom/base/nsGlobalWindow.cpp:10000
19 	xul.dll 	nsGlobalWindow::TimerCallback 	dom/base/nsGlobalWindow.cpp:10267
20 	xul.dll 	nsTimerImpl::Fire 	xpcom/threads/nsTimerImpl.cpp:472
21 	xul.dll 	nsTimerEvent::Run 	xpcom/threads/nsTimerImpl.cpp:555
22 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:620
23 	xul.dll 	mozilla::ipc::MessagePump::Run 	ipc/glue/MessagePump.cpp:117
24 	xul.dll 	MessageLoop::RunHandler 	ipc/chromium/src/base/
25 	xul.dll 	MessageLoop::Run 	ipc/chromium/src/base/
26 	xul.dll 	nsBaseAppShell::Run 	widget/xpwidgets/nsBaseAppShell.cpp:163
27 	xul.dll 	nsAppShell::Run 	widget/windows/nsAppShell.cpp:232
28 	xul.dll 	nsAppStartup::Run 	toolkit/components/startup/nsAppStartup.cpp:290
29 	xul.dll 	XREMain::XRE_mainRun 	toolkit/xre/nsAppRunner.cpp:3799
30 	xul.dll 	XREMain::XRE_main 	toolkit/xre/nsAppRunner.cpp:3866
31 	xul.dll 	XRE_main 	toolkit/xre/nsAppRunner.cpp:3941
32 	firefox.exe 	wmain 	toolkit/xre/nsWindowsWMain.cpp:105

More reports at:*%29
Tracking for now, just to confirm that this spike goes down after beta 4 ships.
Spike went back down, untracking.
It's #9 top browser crasher in 19.0.

It happens almost only with AMD devices: 0x9802, 0x9803, 0x9804, 0x9806, 0x9807, 0x6760 (see for the matching GPUs).
It's the Windows 7 version of bug 830531.
Keywords: topcrash
OS: Windows XP → Windows 7
Summary: crash in js::analyze::ScriptAnalysis::analyzeLifetimes → crash in js::analyze::ScriptAnalysis::analyzeLifetimes mainly with AMD Radeon HD 6250/6290/6310/6320/6400M (Wrestler/Vancouver Asics)
Version: 17 Branch → 19 Branch
Sounds like a similar case to bug 830531 et al. - I think there's a chipset or driver problem behind all that.
This will either be fixed thanks to the investigation in bug 830531 (fixed once and for all), or we won't want to touch FF19.0 given the lower crash volume percentage here as compared to 19.0b5.
If we can find anybody who's able to repro this bug, we should provide them with the first 19.0.1 re-spin including bug 623462.
The fact that this is rising may point to these cards being more prevalent in areas with lower bandwidth (slower update uptake).
Depends on: 772330
20.0b2 is similar to 19.0b6 which leads us to believe this is a crash spike specific to the release build - not something we can track/repro at this time.
It's #116 browser crasher in 20.0.1, #104 in 21.0b3, and #89 in 22.0a2.
Keywords: topcrash
OS: Windows 7 → Windows XP
Assignee: general → nobody
Crash Signature: [@ js::analyze::ScriptAnalysis::analyzeLifetimes(JSContext*)] → [@ js::analyze::ScriptAnalysis::analyzeLifetimes(JSContext*)] [@ js::analyze::ScriptAnalysis::analyzeLifetimes]
Closing because no crash reported since 12 weeks.
Closed: 4 years ago
Resolution: --- → WONTFIX
Closing because no crash reported since 12 weeks.
You need to log in before you can comment on or make changes to this bug.