Closed Bug 865373 Opened 12 years ago Closed 12 years ago

crash in js::ion::LinearScanAllocator::go

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
23 Branch
Platform:
All
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox22 --- unaffected
firefox23 --- affected

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash, regression)

Crash Data

It started spiking in 23.0a1/20130424 and is currently #5 top crasher in this build. The regression range for the spike is: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=acf388eaf9e9&tochange=fef5f202b2dc Signature js::ion::LinearScanAllocator::populateSafepoints() More Reports Search UUID dbda98ad-7513-41e2-af58-2a0ff2130424 Date Processed 2013-04-24 17:09:21 Uptime 1077 Install Age 29.6 minutes since version was first installed. Install Time 2013-04-24 16:39:36 Product Firefox Version 23.0a1 Build ID 20130424030917 Release Channel nightly OS Windows NT OS Version 6.1.7601 Service Pack 1 Build Architecture x86 Build Architecture Info AuthenticAMD family 16 model 4 stepping 3 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x20 App Notes AdapterVendorID: 0x1002, AdapterDeviceID: 0x683d, AdapterSubsysID: 23191787, AdapterDriverVersion: 9.12.0.0 D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+ Processor Notes sp-processor03.phx1.mozilla.com_18643:2012; non-integer value of "SecondsSinceLastCrash"; exploitability tool failed: 127 EMCheckCompatibility True Adapter Vendor ID 0x1002 Adapter Device ID 0x683d Total Virtual Memory 4294836224 Available Virtual Memory 3698860032 System Memory Use Percentage 21 Available Page File 14853820416 Available Physical Memory 6706176000 Frame Module Signature Source 0 mozjs.dll js::ion::LinearScanAllocator::populateSafepoints js/src/ion/LinearScan.cpp:535 1 mozjs.dll js::ion::LinearScanAllocator::go js/src/ion/LinearScan.cpp:1168 2 mozjs.dll js::ion::GenerateLIR js/src/ion/Ion.cpp:1129 3 mozjs.dll js::ion::CompileBackEnd js/src/ion/Ion.cpp:1209 4 mozjs.dll js::WorkerThread::handleIonWorkload js/src/jsworkers.cpp:391 5 mozjs.dll js::WorkerThread::threadLoop js/src/jsworkers.cpp:431 6 mozjs.dll js::WorkerThread::ThreadMain js/src/jsworkers.cpp:332 7 nss3.dll _PR_NativeRunThread nsprpub/pr/src/threads/combined/pruthr.c:395 8 nss3.dll pr_root nsprpub/pr/src/md/windows/w95thred.c:90 9 msvcr100.dll _callthreadstartex f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:314 10 msvcr100.dll _threadstartex f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:292 11 kernel32.dll BaseThreadInitThunk 12 ntdll.dll __RtlUserThreadStart 13 ntdll.dll _RtlUserThreadStart More reports at: https://crash-stats.mozilla.com/report/list?signature=js%3A%3Aion%3A%3ALinearScanAllocator%3A%3ApopulateSafepoints%28%29
More reports also at: https://crash-stats.mozilla.com/report/list?signature=js%3A%3Aion%3A%3ALiveRangeAllocator%3Cjs%3A%3Aion%3A%3ALinearScanVirtualRegister%3E%3A%3AbuildLivenessInfo%28%29
Blocks: 844506
Crash Signature: [@ js::ion::LinearScanAllocator::populateSafepoints()] → [@ js::ion::LinearScanAllocator::populateSafepoints()] [@ js::ion::LiveRangeAllocator<js::ion::LinearScanVirtualRegister>::buildLivenessInfo() ]
Hardware: x86 → All
Summary: crash in js::ion::LinearScanAllocator::populateSafepoints → crash in js::ion::LinearScanAllocator::go
I think these crashes should be fixed by bug 865635.
(In reply to Brian Hackett (:bhackett) from comment #2) > I think these crashes should be fixed by bug 865635. It seems so because there are no crashes in 23.0a1/20130427 and above.
tracking-firefox23: ? → ---
Keywords: topcrash
There are still a few crashes recently but not at the previous volume.
There was only one crash in 23.0a1/20130502 after 23.0a1/20130426 so let's close it as workforme
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.