Flags undefined in tokenize

Hi,

Can’t reproduce it properly, but sometimes when using FileHighlighter plugin we get flags undefined in tokenize. Which leads to RegExp exception, it tries undefinedg.

Since I can’t reproduce when debugging i propose the following:

var flags = pattern.pattern.toString().match(/[imuy]*$/)[0];
pattern.pattern = RegExp(pattern.pattern.source, flags + "g");

Replaced with:

var flags = pattern.pattern.toString().match(/[imuy]*$/)[0];
pattern.pattern = RegExp(pattern.pattern.source, (flags || "") + "g");

Regards, Johan

[zeitgeist87]

The user-agent would suggest, that it is a 64bit Linux system running Chromium 47.0.2526.80 which is over a year old now. Do all these users have the same user-agent? Could it be some kind of crawler that uses a fake user-agent?

The only way for flags to become undefined is if you change either the prototype of RegExp or String. At least as far as I can see. I don’t think we will add these changes if you cannot reproduce the bug, or show a plausible way how flags can be undefined.

Maybe you could add some debug code to your site that provides more information:

if (flags === undefined) {
    console.log(pattern, pattern.pattern, pattern.pattern.toString(), pattern.pattern.toString().match(/[imuy]*$/));
}

[Golmote]

Please reopen if you can provide more information regarding this issue.