Closed Bug 1511415 Opened 7 years ago Closed 2 years ago

Crash in js::jit::ICScript::purgeOptimizedStubs

Categories

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

Unspecified
Windows 10
defect

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox-esr60 --- unaffected
firefox63 --- unaffected
firefox64 --- unaffected
firefox65 --- wontfix
firefox66 --- wontfix
firefox67 --- fix-optional

People

(Reporter: calixte, Unassigned)

References

(Blocks 1 open bug)

Details

(4 keywords, Whiteboard: [#jsapi:crashes-retriage])

Crash Data

This bug was filed from the Socorro interface and is report bp-b96b3b0d-8bd4-4313-bec9-920e50181130. ============================================================= Top 10 frames of crashing thread: 0 xul.dll js::jit::ICScript::purgeOptimizedStubs js/src/jit/BaselineJIT.cpp:1090 1 xul.dll JS::Zone::discardJitCode js/src/gc/Zone.cpp:277 2 xul.dll js::gc::ArenaLists::relocateArenas js/src/gc/GC.cpp:2568 3 xul.dll js::gc::GCRuntime::compactPhase js/src/gc/GC.cpp:7087 4 xul.dll js::gc::GCRuntime::incrementalSlice js/src/gc/GC.cpp:7610 5 xul.dll js::gc::GCRuntime::gcCycle js/src/gc/GC.cpp:7914 6 xul.dll js::gc::GCRuntime::collect js/src/gc/GC.cpp:8095 7 xul.dll JS::IncrementalGCSlice js/src/gc/GC.cpp:9091 8 xul.dll nsJSContext::GarbageCollectNow dom/base/nsJSEnvironment.cpp:1212 9 xul.dll static bool InterSliceGCRunnerFired dom/base/nsJSEnvironment.cpp:1853 ============================================================= There is 1 crash in nightly 65 with buildid 20181129214405. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1499644. [1] https://hg.mozilla.org/mozilla-central/rev?node=6453222232be
Flags: needinfo?(jdemooij)
Just one crash, doesn't look actionable, and I did fix an issue in this area.
Flags: needinfo?(jdemooij)
low volume & not-actionable (comment 1) -> P3
Priority: -- → P3
Whiteboard: [#jsapi:crashes-retriage]

Mix of wildptr and at least one clear UAF address

Probably should be re-triaged

Group: core-security
Flags: needinfo?(sdetar)

nbp: This bug should be re-triaged as per jesup's comment

Flags: needinfo?(sdetar) → needinfo?(nicolas.b.pierron)
Group: core-security → javascript-core-security

We could still take a fix here for 66, is this still considered P3?

(In reply to Liz Henry (:lizzard) (use needinfo) from comment #5)

We could still take a fix here for 66, is this still considered P3?

Nothing changed from comment 2. Yes.

Flags: needinfo?(nicolas.b.pierron)

Jan, this seems to have been growing in FF65. Did we mess with IC handling in that version? I'm trying to remember.

Flags: needinfo?(jdemooij)
See Also: → 1511417

(In reply to Ted Campbell [:tcampbell] from comment #7)

Jan, this seems to have been growing in FF65. Did we mess with IC handling in that version? I'm trying to remember.

We moved ICs from BaselineScript to ICScript in FF65, bug 1499644, so the signature is definitely new.

Looking at the crashes it seems to be memory corruption in the ICStub LifoAlloc. The fallback stubs in the ICScript's LifoAlloc are never freed before the ICScript itself is destroyed. The optimized stubs in the Zone-wide LifoAlloc are, but I can't think of any issues there. We've seen ICStub-related crashes for a long time, might be similar to the TI LifoAlloc ones. I'll think about it more.

Flags: needinfo?(jdemooij)

Unassigned P3, low volume of crashes, so fix-optional for our upcoming release.

Removing employee no longer with company from CC list of private bugs.

Severity: critical → S2
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE

Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit auto_nag documentation.

Keywords: stalled
Group: javascript-core-security
You need to log in before you can comment on or make changes to this bug.