1111694 - regexp: an error occurred while executing regular expression with SyntaxHighlighter JS API

Status: RESOLVED WONTFIX

(Core :: JavaScript Engine, defect)

Description

[Loic]

STR:
Open http://alexgorbatchev.com/SyntaxHighlighter/manual/api/autoloader.html

Result: Both examples with code highlighted are not displayed.

Console error:
an error occurred while executing regular expression shCore.js:17
http://agorbatchev.typepad.com/pub/sh/3_0_83/scripts/shCore.js

Regression range:
good=2014-01-10
bad=2014-01-11
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=37516445a0b5&tochange=e89afc241513

Probably due to bugs:
Till Schneidereit — Bug 953013 - throw exceptions for uncorrectly-interpreted regular expressions instead of treating them as non-matching. r=jandem
or
Till Schneidereit — Bug 952898 - String.prototype.startsWith and .endsWith should throw when called with a regexp as first argument. r=jwalden

Comment 1

[Loic]

This page freezes Firefox due to bug 1111625 (irregexp issue).

till, is it a valid bug in FF about regexp or just an issue in the website code source?

Comment 2

[Till Schneidereit [:till]]

Hmm, in Nightly I don't get an error message in the console. Instead, I get either a permanently unresponsive browser without e10s or a slow script dialog in e10s. However, when I click "stop script" in the slow script dialog, I end up with an unresponsive content process after all.

Brian, can you take a look at why our interrupt mechanism doesn't properly catch this?

Comment 3

[Till Schneidereit [:till]]

Oh, I think I understand now. In older versions of FF, this bug is hit, whereas in newer versions, bug 1111625 is hit.

If that understanding is correct, I don't think there's much we need to do here: we don't support those versions anymore and nobody would implement a fix, even if the issue is on our side. (Which isn't entirely clear to me.)

Comment 4

[Nicolas B. Pierron [:nbp]]

We moved to v8 regexp since … closing.