Comment #18 on issue 20204 by eric.rannaud: High CPU usage on wired.com
article.
http://code.google.com/p/chromium/issues/detail?id=20204
I indented mootools-1.2.1-core-nc.js a bit, with some Perl, to step through
it with
the inspector. See the version attached, lines 119 to 137.
It seems the code goes into some kind of weird loop / recursion, setting up
a timer to
call itself (?) every time. I find it hard to see anything, as the
inspector doesn't
seem to like anonymous functions very much. Anyway, somebody with more JS
and
inspector experience can probably figure out much more than I can.
PS: do you know of a good Javascript indenter? indent(1) screws up the
regexps. Does
Chrome have a built-in way to go around obfuscated JS code all on one very
long line?
Attachments:
mootools-1.2.1-core-nc.js 76.1 KB
--
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
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
