Comment #2 on issue 287 by [email protected]: Long, complex regexp pattern (in WebKit layout test) hangs http://code.google.com/p/v8/issues/detail?id=287
As someone who isn't writing a VM or a regexp engine, I can draw a clear line between writing JS that explicitly takes hours (e.g. an infinite loop, or bubble-sorting the Library of Congress) and using a regular expression that happens to use exponential time behind the scenes. I could imagine, ignorant as I am, having a regexp engine that was optimized for a match like this one and completed it quickly. (I'm not saying that V8's should, just that it's not at all self-evident that one "simple" call should take exponential time.) For reference, one reason to add a timeout for REs is that Safari (JSC) does. If Firefox has a limit, it's beyond the 30 seconds I was willing to let it run. Interestingly, IE finishes the test, including that long piece, in only about 15 seconds. But I haven't looked closely enough at the ugly regexp to see if it gets the right answer. More practically, Chromium still wants to be able to run this layout test so we don't lose coverage of the other pieces. And we're trying very hard not to keep forked tests. I'm willing to try to talk WebKit into removing this part, but they don't have much incentive. Any other suggestions? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
