Bug 106735
| Summary: | [Chromium]A simple JavaScript infinite loop page caues chrome browser CPU load 50% on my Dual-Core E7400 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Chen Zhixiang <chenzx> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Critical | CC: | schenney |
| Priority: | P4 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Chen Zhixiang
Test file:
<body>
<script>
d=Number.NEGATIVE_INFINITY;
while(1){
d = d+0.000001;
}
</script>
</body>
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Chen Zhixiang
I was willing to submit bug to http://code.google.com/p/chromium/issues/list
But China GFW blocked *.appspot.com,
so i submit it here
While, as to this case, Firefox can immediately popup a dialog to permit user to terminated JS executing.
That is to say, Firefox 18's IonMonkey seems greater than Google Chrome's v8?
Chen Zhixiang
QtWebKit can detect this js loop problem is 2~3s
I think maybe google v8 is too confident in performance that it missed some detect?