Comment #26 on issue 430 by l...@google.com: Regex hardlock
http://code.google.com/p/v8/issues/detail?id=430
The real problem here is that Chrome/V8 tries to implement the actual
behavior of the ECMAScript specification, which leads to the exponential
execution time that you are seeing.
What other implementations are doing instead is to make an arbitrary
cut-off point, and if you are doing to much work, they give up and say that
it doesn't match. That is actually incorrect behavior. I'd prefer if they
threw an exception in that case instead, saying "overlong RegExp
computation aborted". That would cue in the writer to the actual problem,
instead of just getting false negatives in a few cases.
Chrome should not just lock up - it should eventually show a "long running
script" alert, and allow you to interrupt it, just as it would
for "while(true);". If that doesn't happen, there is a problem
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
