Closed Bug 1650109 Opened 8 months ago Closed 8 months ago

Crash in [@ v8::internal::TextNode::TextEmitPass]

Categories

(Core :: JavaScript Engine, defect, P1)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox80 --- wontfix

People

(Reporter: jcristau, Unassigned)

References

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-9e0797db-fe98-4a66-a675-6c55b0200702.

Top 10 frames of crashing thread:

0 xul.dll v8::internal::TextNode::TextEmitPass js/src/irregexp/imported/regexp-compiler.cc:2307
1 xul.dll v8::internal::TextNode::Emit js/src/irregexp/imported/regexp-compiler.cc:2430
2 xul.dll v8::internal::ChoiceNode::EmitChoices js/src/irregexp/imported/regexp-compiler.cc:3239
3 xul.dll v8::internal::ChoiceNode::Emit js/src/irregexp/imported/regexp-compiler.cc:3051
4 xul.dll v8::internal::ActionNode::Emit js/src/irregexp/imported/regexp-compiler.cc
5 xul.dll v8::internal::ChoiceNode::EmitOutOfLineContinuation js/src/irregexp/imported/regexp-compiler.cc:3281
6 xul.dll v8::internal::ChoiceNode::Emit js/src/irregexp/imported/regexp-compiler.cc:3069
7 xul.dll v8::internal::RegExpCompiler::Assemble js/src/irregexp/imported/regexp-compiler.cc:249
8 xul.dll js::irregexp::CompilePattern js/src/irregexp/RegExpAPI.cpp:527
9 xul.dll static js::RegExpShared::execute js/src/vm/RegExpObject.cpp:701

Seeing a number of reports on the 20200701093012 build.

There were no changes to this code in the timeframe of the bug. I looked through the crash reports and nothing stood out to me. If we don't see similar failures on other builds, I'm inclined to believe it was an issue with the build itself. Maybe some sort of PGO issue?

The fact that there is a single build-id definitely hint to a compilation issue.
We should reopen this bug if this bug re-appear in the future.

Severity: -- → S2
Status: NEW → RESOLVED
Closed: 8 months ago
Priority: -- → P1
Resolution: --- → INCOMPLETE
See Also: → 1650254
See Also: 1650254
Duplicate of this bug: 1650254
You need to log in before you can comment on or make changes to this bug.