Crash in [@ OOM | unknown | js::AutoEnterOOMUnsafeRegion::crash | v8::internal::(anonymous namespace)::BytecodeSequenceNode::BytecodeSequenceNode]
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
People
(Reporter: worcester12345, Unassigned)
References
(Blocks 1 open bug)
Details
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/53c72b7c-cf28-4a7b-b67f-fd2120220103
Reason: EXCEPTION_BREAKPOINT
Top 10 frames of crashing thread:
0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1234
1 xul.dll v8::internal::`anonymous namespace'::BytecodeSequenceNode::BytecodeSequenceNode js/src/irregexp/imported/regexp-bytecode-peephole.cc:283
2 xul.dll v8::internal::`anonymous namespace'::BytecodeSequenceNode::FollowedBy js/src/irregexp/imported/regexp-bytecode-peephole.cc:289
3 xul.dll static v8::internal::RegExpBytecodePeepholeOptimization::OptimizeBytecode js/src/irregexp/imported/regexp-bytecode-peephole.cc:1013
4 xul.dll v8::internal::RegExpBytecodeGenerator::GetCode js/src/irregexp/imported/regexp-bytecode-generator.cc:379
5 xul.dll v8::internal::RegExpCompiler::Assemble js/src/irregexp/imported/regexp-compiler.cc:281
6 xul.dll js::irregexp::CompilePattern js/src/irregexp/RegExpAPI.cpp:670
7 xul.dll static js::RegExpShared::execute js/src/vm/RegExpObject.cpp:642
8 xul.dll js::RegExpMatcher js/src/builtin/RegExp.cpp:1172
9 xul.dll Interpret js/src/vm/Interpreter.cpp:3243
Comment 1•4 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 revert this change in case you think the bot is wrong.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
None of the irregexp code here has changed recently. A spike in crashes implies that the regexps we're compiling got bigger / worse somehow: either a website issue, or maybe something changed in browser code. The only meaningful change between 95.0.1 and 95.0.2 appears to be bug 1744287, which doesn't look like a plausible culprit, so I lean towards thinking that any problem here is due to website changes. We can keep an eye on the numbers to see if anything changes.
Updated•4 years ago
|
Comment 3•3 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Updated•1 year ago
|
Comment 4•3 months ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•