Crash in [@ OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash | v8::internal::RegExpStack::EnsureCapacity]
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
People
(Reporter: worcester12345, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: memory-leak, perf)
Crash Data
98.0b9 (64-bit)
Maybe Fission related. (DOMFissionEnabled=1)
Crash report: https://crash-stats.mozilla.org/report/index/d0ace1de-9f5b-44d8-941f-9668a0220225
Reason: EXCEPTION_BREAKPOINT
Top 4 frames of crashing thread:
0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1258
1 xul.dll v8::internal::RegExpStack::EnsureCapacity js/src/irregexp/imported/regexp-stack.cc:96
2 xul.dll js::irregexp::GrowBacktrackStack js/src/irregexp/RegExpAPI.cpp:769
3 None @0x00000141811d4291
|
||
Updated•3 years ago
|
|
|
||
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::JavaScript Engine' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•3 years ago
|
||
This is just an out-of-memory crash in the regexp engine. If anything, it looks like the crash rate has decreased over time. We share our regexp engine with V8, so in cases where we crash, it's likely that Chrome would also crash.
I don't think there's any useful action to be taken here.
|
|
||
Comment 4•3 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Description
•