Open Bug 1676816 Opened 5 years ago Updated 4 years ago

Crash in [@ js::jit::WarpBuilder::buildBody]

Categories

(Core :: JavaScript Engine: JIT, defect, P5)

defect

Tracking

()

Tracking Status
firefox-esr78 --- unaffected
firefox82 --- unaffected
firefox83 --- affected
firefox84 --- affected

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Low frequency, new in Gecko 83.

Crash report: https://crash-stats.mozilla.org/report/index/2b1c614c-3938-4a00-b0dc-091410201111

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0 xul.dll js::jit::WarpBuilder::buildBody js/src/jit/WarpBuilder.cpp:680
1 xul.dll js::jit::WarpBuilder::build js/src/jit/WarpBuilder.cpp:299
2 xul.dll js::jit::AnalyzeArgumentsUsage js/src/jit/IonAnalysis.cpp:4753
3 xul.dll Interpret js/src/vm/Interpreter.cpp:3623
4 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:635
5 xul.dll JS_CallFunctionValue js/src/jsapi.cpp:2766
6 xul.dll nsXPCWrappedJS::CallMethod js/xpconnect/src/XPCWrappedJSClass.cpp:970
7 xul.dll PrepareAndDispatch xpcom/reflect/xptcall/md/win32/xptcstubs.cpp:79
8 xul.dll SharedStub xpcom/reflect/xptcall/md/win32/xptcstubs.cpp:98
9 xul.dll nsXREDirProvider::DoStartup toolkit/xre/nsXREDirProvider.cpp:952

Jan, is there anything actionable in these crash reports?

Side question, do we still require the Arguments Usage analysis knowing that we are no longer relying on TI?

Flags: needinfo?(jdemooij)

I looked at some of these reports but there's not much to go on. The one in comment 0 has an uptime of 0 seconds, that suggests some kind of external/hardware issue.

(In reply to Nicolas B. Pierron [:nbp] {pto until 7/12} from comment #1)

Side question, do we still require the Arguments Usage analysis knowing that we are no longer relying on TI?

Yeah it's still there but it's now based on WarpBuilder. It would be nice to remove the arguments analysis (it also shows up in profiles), maybe that can happen next year...

Flags: needinfo?(jdemooij)

The severity field is not set for this bug.
:sdetar, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(sdetar)
Severity: -- → S3
Flags: needinfo?(sdetar)
Severity: S3 → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.