[chromium-bugs] Issue 288 in chromium: Inspector taking too much CPU

Comment #9 on issue 288 by jor...@incometaxplus.net: Inspector taking too much CPU http://code.google.com/p/chromium/issues/detail?id=288 [CONFIRMED] -- 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

[chromium-bugs] Issue 288 in chromium: Inspector taking too much CPU

Comment #8 on issue 288 by divi...@hotmail.com: Inspector taking too much CPU http://code.google.com/p/chromium/issues/detail?id=288 With 1.0.154.58, CPU usage is not that bad. It does not stay at 50% for long. But still, it should use less memory. -- You received this message because you a

[chromium-bugs] Issue 288 in chromium: Inspector taking too much CPU

Issue 288: Inspector taking too much CPU http://code.google.com/p/chromium/issues/detail?id=288 Comment #5 by arthur2001: I get the same issue on my Vista Basic SP1 running on Core 2 Duo CPU. CPU charge comes up to 50% when I open Object Inspector. It should be up to 100% on single core CPUs.

[chromium-bugs] Issue 288 in chromium: Inspector taking too much CPU

Issue 288: Inspector taking too much CPU http://code.google.com/p/chromium/issues/detail?id=288 Comment #4 by [EMAIL PROTECTED]: Actually, I think this belongs in Area-WebKit as the inspector is part of WebKit. Issue attribute updates: Labels: -Area-BrowserBackend Area-WebKit -- You