No pattern JS GC crash in Nightly 43a1

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
3 years ago
3 years ago

People

(Reporter: zxspectrum3579, Unassigned)

Tracking

({crash})

43 Branch
x86_64
Windows 7
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20150819030206

Steps to reproduce:

I was away from the browser, it was doing in the regular background timer JS operations


Actual results:

The browser has crashed: https://crash-stats.mozilla.com/report/index/8aec8abb-c3fa-447a-a173-720802150820


Expected results:

Normal continuous operation
(Reporter)

Updated

3 years ago
Component: Untriaged → JavaScript: GC
OS: Unspecified → Windows 7
Product: Firefox → Core
Hardware: Unspecified → x86_64
(Reporter)

Updated

3 years ago
Crash Signature: js::jit::StopAllOffThreadCompilations(JS::Zone*)

Updated

3 years ago
Severity: normal → critical
Crash Signature: js::jit::StopAllOffThreadCompilations(JS::Zone*) → [@ js::jit::StopAllOffThreadCompilations(JS::Zone*) ]
Keywords: crash

Comment 1

3 years ago
Do you still experience this crash?

afaict you haven't crashed with this signature since at least Oct 8. And there are no other crash reports for this signature in the last 28 days https://crash-stats.mozilla.com/report/list?product=Firefox&range_unit=days&range_value=28&signature=js%3A%3Ajit%3A%3AStopAllOffThreadCompilations%28JS%3A%3AZone%2A%29#tab-reports 

If there are no steps to reproduce I suggest we close this, as your recent crashes would be more fruitful places to focus. Though it might be better if your reports had steps and involved fewer addons


(In reply to User Dderss from comment #0)
> bp-8aec8abb-c3fa-447a-a173-720802150820

 0 	xul.dll	js::jit::StopAllOffThreadCompilations(JS::Zone*)	js/src/jit/Ion.cpp
1 	xul.dll	js::gc::GCRuntime::compactPhase(JS::gcreason::Reason, js::SliceBudget&)	js/src/jsgc.cpp
2 	xul.dll	js::gc::GCRuntime::incrementalCollectSlice(js::SliceBudget&, JS::gcreason::Reason)	js/src/jsgc.cpp
3 	xul.dll	js::gc::GCRuntime::gcCycle(bool, js::SliceBudget&, JS::gcreason::Reason)	js/src/jsgc.cpp
4 	xul.dll	js::gc::GCRuntime::collect(bool, js::SliceBudget, JS::gcreason::Reason)	js/src/jsgc.cpp
5 	xul.dll	js::gc::GCRuntime::gc(JSGCInvocationKind, JS::gcreason::Reason)	js/src/jsgc.cpp
6 	xul.dll	`anonymous namespace'::GarbageCollectRunnable::WorkerRun(JSContext*, mozilla::dom::workers::WorkerPrivate*)	dom/workers/WorkerPrivate.cpp
7 	xul.dll	mozilla::dom::workers::WorkerRunnable::Run()	dom/workers/WorkerRunnable.cpp
8 	xul.dll	mozilla::dom::workers::WorkerPrivate::ProcessAllControlRunnablesLocked()	dom/workers/WorkerPrivate.cpp
9 	xul.dll	mozilla::dom::workers::WorkerPrivate::DoRunLoop(JSContext*)	dom/workers/WorkerPrivate.cpp
10 	xul.dll	`anonymous namespace'::WorkerThreadPrimaryRunnable::Run()	dom/workers/RuntimeService.cpp
11 	xul.dll	nsThread::ProcessNextEvent(bool, bool*)	xpcom/threads/nsThread.cpp
12 	xul.dll	NS_ProcessNextEvent(nsIThread*, bool)	xpcom/glue/nsThreadUtils.cpp
13 	xul.dll	mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*)	ipc/glue/MessagePump.cpp
14 	xul.dll	MessageLoop::RunHandler()	ipc/chromium/src/base/message_loop.cc
15 	xul.dll	MessageLoop::Run()	ipc/chromium/src/base/message_loop.cc
16 	xul.dll	nsThread::ThreadFunc(void*)	xpcom/threads/nsThread.cpp
17 	nss3.dll	PR_NativeRunThread	nsprpub/pr/src/threads/combined/pruthr.c
18 	nss3.dll	pr_root	nsprpub/pr/src/md/windows/w95thred.c
19 	msvcr120.dll	_callthreadstartex	f:\dd\vctools\crt\crtw32\startup\threadex.c:376
20 	msvcr120.dll	_threadstartex	f:\dd\vctools\crt\crtw32\startup\threadex.c:354
21 	kernel32.dll	BaseThreadInitThunk	
22 	ntdll.dll	RtlUserThreadStart	
23 	kernel32.dll	BasepReportFault	
24 	kernel32.dll	BasepReportFault
Flags: needinfo?(zxspectrum3579)
(Reporter)

Comment 2

3 years ago
Yes, there were no crashes like this since then, especially because I switched to e10s mode, which is vastly different. But there is no way to reproduce the bug anyway since it occurred without changes in the set of add-ons/extensions, and without me visiting some specifically atypical pages. 

So what has happened at the moment of crashes is some unknown script of some unknown site that was crashing FireFox -- alas, not reproducible any more.
Flags: needinfo?(zxspectrum3579)

Comment 3

3 years ago
let's call it incomplete, and if it happens again we can repopen
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.