3 ms·
It's choking on this regex with a "too much recursion" error: var match = data.match(/([\s\S]+?)<div data-is-preview.+?>([\s\S]+)<\/div>/m);
by dsissitka 2y ago
It's choking on this regex with a "too much recursion" error:
var match = data.match(/([\s\S]+?)<div data-is-preview.+?>([\s\S]+)<\/div>/m);
- gpvos 2y agoSame here.
- Brybry 2y agoThere's a Firefox bugzilla entry for it: https://bugzilla.mozilla.org/show_bug.cgi?id=1845775 https://bugzilla.mozilla.org/show_bug.cgi?id=1845775 And a (closed in favor of the bugzilla entry) webcompat issue: https://github.com/webcompat/web-bugs/issues/125193 https://github.com/webcompat/web-bugs/issues/125193
- capitainenemo 2y agoUh... wow. https://bugzilla.mozilla.org/show_bug.cgi?id=1845775#c14 https://bugzilla.mozilla.org/show_bug.cgi?id=1845775#c14 "Long story short: the watchdog thread interrupted us four times, so we gave up and threw an error. This also explains why Chrome is significantly faster here: when interrupted, we stop the regexp, handle the interrupt, then restart regexp execution from the beginning, whereas V8 does scary code crimes to keep the regexp running despite the possibility of triggering a GC with unrooted values on the stack. (The words "manually relocate unhandlified references" are involved.)" That doesn't sound good...