Crash [@ js::RegExpStatics::getRightContext] after slow script dialog and Assertion failure: !pendingLazyEvaluation

RESOLVED INCOMPLETE

Status

()

Core
JavaScript Engine
--
critical
RESOLVED INCOMPLETE
5 years ago
2 years ago

People

(Reporter: neil@parkwaycc.co.uk, Unassigned)

Tracking

({crash, stackwanted})

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

Comment hidden (empty)
(Reporter)

Updated

5 years ago
Summary: Crash @ js::RegExpStatics:: → Crash [@ js::RegExpStatics::getRightContext] after slow script dialog
(Reporter)

Comment 1

5 years ago
I was browsing using a debug build that I compiled last Friday and a slow script dialog was triggered. I clicked to continue the script and then I hit an Assertion failure: !pendingLazyEvaluation and the process crashed.
If the crash report was submitted, could you browse to "about:crashes" and copy/paste the link to the crash report into this bug?
(Reporter)

Comment 3

5 years ago
Crash reports don't make sense for local builds... unfortunately I neglected to take a stack trace or anything useful like that, which is why I filed as UNCO.

Updated

5 years ago
Severity: normal → critical
Keywords: crash, stackwanted
Summary: Crash [@ js::RegExpStatics::getRightContext] after slow script dialog → Crash [@ js::RegExpStatics::getRightContext] after slow script dialog and Assertion failure: !pendingLazyEvaluation

Comment 4

2 years ago
unfortunately without a reproducible testcase and a stacktrace this isn't going anywhere. And the 2 stack signatures (only two) from the past month aren't useful. So closing
Status: UNCONFIRMED → RESOLVED
Crash Signature: [@ js::RegExpStatics::getRightContext]
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.