Issue 141178 in chromium: High CPU usage of Browser process in Chrome Task manager

[c***@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined OS-Windows

New issue 141178 by ***@gmail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Chrome Version : 21.0.1180.75
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: OK
Firefox 4.x: OK
IE 7/8/9: OK

What steps will reproduce the problem?
There is no stable steps. This can be some extensions is in process that
cause high CPU.

1. Launch chrome
2. Use it for some time


What is the expected result?
Low CPU usage while idle

What happens instead?
Notice that one of the Chrome instances in the system task manager
consuming whole core performance. Browsing is not affected. Everything is
fast.

On attached screenshot You can see that Browser process consuming 13%.
That's because processor is 8 core.

Here is a 7zip compressed dump created with process explorer if needed:
http://files.alfeg.net/chrome.7z

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1
(KHTML, like Gecko) Chrome/21.0.1180.75 Safari/537.1

Attachments:
9gkmx1[1].png 95.1 KB

[c***@googlecode.com]

Comment #8 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

In r144412 we rolled leveldb to pick up a fix in r66
http://code.google.com/p/leveldb/source/detail?r=075a35a6d390167b77b687e067dd0ba593e7f624
in which I/O errors could send leveldb into a tight loop in the background
compaction thread. This would manifest as
leveldb::DBImpl::BackgroundCompaction being called, failing due to I/O
error (e.g. CreateFile failing), then being re-called immediately. The
leveldb fix was to introduce an arbitrary delay before retrying (1s, I
believe). That appears to be compatible with the above stack.

If this is persisting through browser restarts and there's no obvious
filesystem issue (e.g. user profile is not in an NFS homedir that's no
longer mounted) then a workaround would be to remove the IndexedDB
directory from the profile; possibly something has been corrupted.

[c***@googlecode.com]

Comment #9 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Looks like M21 stable is r142910 so this seems like a likely candidate.
Note that it doesn't fix the underlying issue, but prevents the thread from
consuming CPU when the issue occurs. Related bug 125641 tracks more
graceful error handling which would allow web apps to report errors to the
user.

[c***@googlecode.com]

Comment #10 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

I've deleted all IndexedDB folders from profiles.

Bug still persist on restarts.

Here is a minidump attached.
You mention that there can be error in IndexedDB folder, so I've attached
it too.

PS: I've forgot to mention, that one of profiles is located on another
disk, and linked via NTFS links using Junction from MS TechNet. I've done
this cause second disk is much faster than system, and not so much apps
using it.

PSS: If it helps, I've uploaded original dump compressed with plain Zip:
http://files.alfeg.net/chrome.dmp.zip




Attachments:
chrome.zip 408 KB
https_docs.google.com_0.indexeddb.leveldb.7z 1.2 MB

[c***@googlecode.com]

Comment #11 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Chrome://profiler data attached


Attachments:
14abb785-768e-46ed-8c4e-9fe4a42bbab4 634 KB

[c***@googlecode.com]

Updates:
Cc: ***@chromium.org ***@chromium.org
Labels: WebKit-Storage

Comment #12 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Interesting that the bug persists on restart. (Did the Chrome process
really exit, or was there still something running in the background?) Does
the new minidump still point at leveldb?

If it's still leveldb I wonder if there's an extension using IndexedDB or
FileSystem so the issue is triggered on startup. Any indication of what
extension or site you're hitting that might be inducing it?

The note about the profile being on another disk is very interesting. It
would be interesting to experiment with profiles pointing at your main
disk. (Unfortunately, I won't have access to a Windows box for a few days
so I won't be able to immediately experiment myself.)

Also, would it be possible to try a Dev channel or Canary build of Chrome
to see if the leveldb fix we mention above addresses the issue?

[c***@googlecode.com]

Comment #13 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

The minidump in comment #10 shows the same callstack as before (listed
below).
@ericu: The process ID and uptime in the dumps are consistent with a
restart, so I don't believe there was a lingering shutdown issue.

091df4f0 5c5099e5 kernel32!ReadFileImplementation+0xf0
091df520 5d7d2394 chrome_5bfc0000!base::ReadPlatformFile+0x48
[c:\b\build\slave\win\build\src\base\platform_file_win.cc @ 129]
091df550 5d7d33db chrome_5bfc0000!leveldb::`anonymous
namespace'::ChromiumRandomAccessFile::Read+0x25
[c:\b\build\slave\win\build\src\third_party\leveldatabase\env_chromium.cc @
184]
091df5c4 5d7d2c71 chrome_5bfc0000!leveldb::ReadBlock+0x4e
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\table\format.cc
@ 80]
091df638 5d7d298e chrome_5bfc0000!leveldb::Table::BlockReader+0xd2
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\table\table.cc
@ 120]
091df664 5d7d2ab5 chrome_5bfc0000!leveldb::`anonymous
namespace'::TwoLevelIterator::InitDataBlock+0x62
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\table\two_level_iterator.cc
@ 165]
091df670 5d7d1308 chrome_5bfc0000!leveldb::`anonymous
namespace'::TwoLevelIterator::SeekToFirst+0x1b
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\table\two_level_iterator.cc
@ 101]
091df688 5d7cb413 chrome_5bfc0000!leveldb::`anonymous
namespace'::MergingIterator::SeekToFirst+0x20
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\table\merger.cc
@ 37]
091df7cc 5d7cc08b chrome_5bfc0000!leveldb::DBImpl::DoCompactionWork+0xcb
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\db\db_impl.cc
@ 842]
091df90c 5d7cc1aa
chrome_5bfc0000!leveldb::DBImpl::BackgroundCompaction+0x315
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\db\db_impl.cc
@ 665]
091df918 5d7d259e chrome_5bfc0000!leveldb::DBImpl::BackgroundCall+0x1a
[c:\b\build\slave\win\build\src\third_party\leveldatabase\src\db\db_impl.cc
@ 613]
091df94c 091df968 chrome_5bfc0000!leveldb::`anonymous
namespace'::ChromiumEnv::BGThread+0x66
[c:\b\build\slave\win\build\src\third_party\leveldatabase\env_chromium.cc @
539]
091df950 5d7d20a7 0x91df968
091df95c 5bfe8942 chrome_5bfc0000!leveldb::`anonymous
namespace'::Thread::ThreadMain+0x9
[c:\b\build\slave\win\build\src\third_party\leveldatabase\env_chromium.cc @
495]
091df968 7681339a chrome_5bfc0000!base::`anonymous
namespace'::ThreadFunc+0x1b
[c:\b\build\slave\win\build\src\base\threading\platform_thread_win.cc @ 60]
091df974 77209ef2 kernel32!BaseThreadInitThunk+0xe
091df9b4 77209ec5 ntdll_771d0000!__RtlUserThreadStart+0x70
091df9cc 00000000 ntdll_771d0000!_RtlUserThreadStart+0x1b

[c***@googlecode.com]

Comment #16 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

It would be interesting to experiment with profiles pointing at your
main disk

Have moved all profiles to same place. Bug persist.

Has done a big bunch of tests. Deleted files from profile one by one, and
restarting Chrome.

Found that after deleting Local State file from user data directory chrome
behave as expected without high CPU usage.

I've attached this bad file(size: 17 292 bytes), and good one(size: 5 239
bytes), created by Chrome after deleting.


Attachments:
Local State 16.9 KB
Local State 5.1 KB

[c***@googlecode.com]

Comment #17 on issue 141178 by ***@gmail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

After deleting IndexedDB and Local State, the problem persists on my PC. I
tried enabling and disabling extensions and finally found that it's adblock
plus(BETA) that causes the problem. After deleting and reinstalling adblock
plus (BETA). The high cpu problem never occurred again.

[c***@googlecode.com]

Comment #20 on issue 141178 by ***@gmail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

I noticed a similar problem tonight... my Macbook's fan was suddenly
running inexplicably hard.

OSX 10.7.4, Chrome 21.0.1180.77 beta

Discovered three spinning Chrome processes:
1) Browser (pid 66023)
2) Extension: Keep My Opt-Outs (pid 66031)
3) Extension: IBA Opt-out (by Google) (pid 66028)

So the opt-out extensions are fighting? I don't know if this is the same
bug.

I have other extensions, but they are using 0.0% CPU: AdBlock, Instachrome,
RSS Subscription Extension

I closed all my tabs, cleared my cookies/cache/history, and restarted
Chrome (verifying that it did indeed shutdown completely). Problem persists
even with no tabs (just one blank tab, that is).

Went to chrome://profiler after a minute, and saved stats (attached).

I kill -SEGV'ed the three processes that were consuming CPU, producing
these crash IDs:

Aug 14 03:20:28 loftsalir ReportCrash[66128]: Saved crash report for Google
Chrome Helper[66031] version 21.0.1180.77 (1180.77) to
/Users/mday/Library/Logs/DiagnosticReports/Google Chrome
Helper_2012-08-14-032027_loftsalir.crash
Aug 14 03:20:28 loftsalir ReportCrash[66128]: Saved crash report for Google
Chrome Helper[66028] version 21.0.1180.77 (1180.77) to
/Users/mday/Library/Logs/DiagnosticReports/Google Chrome
Helper_2012-08-14-032028_loftsalir.crash
Aug 14 03:20:28 loftsalir com.apple.launchd.peruser.501[111]
([0x0-0x191b91a].com.google.Chrome[66023]): Job appears to have crashed:
Segmentation fault: 11
Aug 14 03:20:28 loftsalir ReportCrash[66128]: Saved crash report for Google
Chrome[66023] version 21.0.1180.77 (1180.77) to
/Users/mday/Library/Logs/DiagnosticReports/Google
Chrome_2012-08-14-032028_loftsalir.crash

Attachments:
ad2f4617-fc79-493a-97c4-5a5be2ecf97f 417 KB

[c***@googlecode.com]

Comment #21 on issue 141178 by ***@gmail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Followup to comment 20:

1) I deleted Keep My Opt-Outs, but the other extension (IBA Opt-out)
continued spinning using max CPU. (even after restarting)

2) So, I deleted IBA Opt-out as well, and now my Chrome is finally idle.

3) Then I reinstalled Keep My Opt-Outs and Chrome is still idle.

4) Ah, but when I then install IBA Opt-out, the CPU usage of both IBA
Opt-out and Keep My Opt-Outs shoots back up to max.

5) So I uninstalled both. Back to idle.

6) Ah, if I install just IBA Opt-out, its CPU usage shoots up to max.

Conclusion: I can have Keep My Opt-Outs installed without issue, but not
IBA Opt-out. I will do that I guess.

Note: I have used both these extensions together for at least a year
without problems. Is there some new reason why I can't use both at the same
time?

[c***@googlecode.com]

Comment #22 on issue 141178 by ***@gmail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

It's probably worth noting that the IBA Opt-out extension was updated to
version 1.2 today, August 14, 2012.

[c***@googlecode.com]

Comment #23 on issue 141178 by ***@gmail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

I found the Google Code project for the IBA Opt-out plugin and filed a bug
there:

http://code.google.com/p/google-opt-out-plugin/issues/detail?id=22

[c***@googlecode.com]

Comment #32 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Same problem here.
1 core has always 100%. this leads my fan to be very loud.

Chrome: 21.0.1180.89 m
Windows 8
8 thread CPU

[c***@googlecode.com]

Comment #33 on issue 141178 by ***@chromium.org: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

re: comment 32 (Michael)

You should check your Chrome Task Manager, and see if it is some secondary
process gone wild, such as flash.

If you don't see a "special" process that is taking up all the CPU time,
then I'd appreciate it if you'd visit the about:profiler page, and then
save your profiler file (there is a button at the top). If you could post
the profiler result to this bug, we could take a look at it. The profiler
output file does not contain any personal information, and just shows what
tasks (functions) are getting called, and how many times.

[c***@googlecode.com]

Comment #34 on issue 141178 by ***@hotmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Here's my profiler, if it helps. Browser process is often at 13% of my
entire computer's CPU usage. I recently reinstalled Chrome and the errors
still persisted even with my initial lack of extensions.

Attachments:
5942f476-2d6c-4717-a2b7-395c410e51c1 706 KB

[c***@googlecode.com]

Comment #35 on issue 141178 by empee584: High CPU usage of Browser process
in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Woo0ow all hail the CHROMIUM TASK MANAGER (Shift+Escape)!
There were too instances of some domain parking #### site clogging memory
(2*1.8GiB and ever growing!?) and fully loading my quad-core (WTF). Task
Manager => <headshot> => <double kill> => peace. Ouch. Worth taking notice
of, this fine tool, THX!
As to the bug: browser thread was stuck at 30%-50%, now I killed another
1+GiB memory tab and browser cpu is at 10%-15%...mmh.

[c***@googlecode.com]

Updates:
Status: Available
Owner: ---

Comment #36 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Dropping myself as owner as there's nothing actionable for IndexedDB or
leveldb here.

[c***@googlecode.com]

Comment #37 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

I've had a similar problem, although for me, it DOES slow down everything
that Chrome does. My profiler data is attached here:

Attachments:
cb0fd98d-2e76-4083-9f42-6928050f4b39 330 KB

[c***@googlecode.com]

Updates:
Cc: ***@chromium.org ***@chromium.org

Comment #38 on issue 141178 by ***@chromium.org: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

re: comment 34, and profiler download ending ...51C1.

I can see something strange going on in your profile. One example is:
net::DhcpProxyScriptAdapterFetcher::Fetch
Which in one case, took a remarkable 83 seconds to run. It also ran 32
times, averaging about 13 seconds per run. Speaking with ERoman, he suggest
that this slowness should not have induced high CPU tallies... but it is
still quite concerning. He suggests supplying a net-internals dump to try
to look closer.
That example also has 171 calls to
net::HostResolverImpl::ProcTask::StartLookupAttempt, each averaging over a
second, and that too is concerning. Both of those suggest slower than
desirable load time... but they should be blocked while waiting, and not
run up CPU levels.

For CPU usage, perhaps the next most heavy user of Total Time is
GpuChannel::OnScheduled with over 102 seconds spent, in over 180K runs...
but the only alarming note there is that one run took 438ms.

It was also interesting to see that a healthy number of tasks run on the
browser's main thread had MaxQueueTime of over 6 seconds. Amazingly, no
single task took more than 747ms to run on (and hence block) the main
thread. That suggests that the CPU was very busy (and starved the UI/main
thread for a while). Any chance you were running on a single core machine
that was wedged by some other process... like the flash process?

I've copied a few folks that may better illuminate some of the tasks that
stuck out.

[c***@googlecode.com]

Comment #39 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

GpuChannel::OnScheduled is part of the GPU process and will not be a factor
in the Browser Process being pegged.

From a quick look at the different profiler results
(...51c1, ...f97f, ...bab4), there doesn't seem to be a common top running
function, so there could be more than one bug here.

I'll keep an eye on this issue, but I don't think it's related to the GPU
process.

[c***@googlecode.com]

Comment #40 on issue 141178 by ***@hotmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

#38 and #39, a recent chrome update completely fixed my problems, and I
don't have that issue appearing any more. So whatever has been done has
fixed my issue. So I don't think my profiler is as important as the others.

[c***@googlecode.com]

Comment #42 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

I have had streaming video stutter and lag issues on Chrome due to the fact
that it is taking up 100% of my CPU performance. Up til then I have not had
any issues with Chrome browser and have not made any major changes or
additions to my pc. I did some research and found by disabling one of the
Shockwave Flash plug-ins, the streaming video now works fine. Just wanted
to let you know this is an issue other users have experienced, perhaps its
a bug?

[c***@googlecode.com]

Comment #50 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Another addendum to #47 and #48:
I was able to reproduce all of the described behavior with all extensions
temporarily disabled using the "--disable-extensions" switch and with
Google Print and Sychronisation turned off. Chrome then starts with three
processes only, but the KERNEL CPU usage remains the same, as does the USER
CPU usage. Memory usage remains a little lower of course.
All Chrome processes terminate just fine when I close the last tab /
browser window in this scenario. With extensions enabled as originally
described, one set of renderer and extensions remains in memory even if no
windows is open. In my case due to a number of extensions, that means that
15 chrome.exe threads using a total of 200-300 MB remain active. But
apparently, the culprit here is an extension. On the other hand, even a
misbehaving extension should not stop chrome from quitting.

[c***@googlecode.com]

Comment #51 on issue 141178 by ***@ymail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Chrome version: 26.0.1397.2
OS: Windows 7 32 bit
CPU: Core 2 Duo E6550 2.33GHz

I also encounter this problem for several months. The CPU usage remains at
about 50% most of the time even if all other processes (GPU and plugins)
are terminated.

Attachments:
Chrome.PNG 37.2 KB

[c***@googlecode.com]

Comment #52 on issue 141178 by ***@ymail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

I encountered this problem before. It solves after a complete
uninstallation (including user profile). The CPU usage becomes normal again
after installing Chrome again (Idle 50% > Idle 1-3%)

[c***@googlecode.com]

Comment #53 on issue 141178 by ***@ymail.com: High CPU usage of Browser
process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

I encountered this problem before. It solves after a complete
uninstallation. The CPU usage of the main process becomes normal again
after reinstallation of Chrome (previously 50% when idle with all Chrome
process except main process terminated, now 1-3% when idle)

[c***@googlecode.com]

Comment #55 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Update:
After four days of use with noticably lower CPU utilisation, Chrome has
reverted to the previous state, i.e. I again see a constant Kernel CPU
utilisation of approx. 10-15% plus a constant User CPU utilisation of
5-15%, meaning total CPU utilisation in the Windows Task Manger is
constantly between 15 and 30%.

[c***@googlecode.com]

Comment #64 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

Issue 362318 has been merged into this issue.
--
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

[c***@googlecode.com]

Updates:
Labels: OS-Linux

Comment #65 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
http://code.google.com/p/chromium/issues/detail?id=141178

(No comment was entered for this change.)
--
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

[c***@googlecode.com]

Comment #66 on issue 141178 by ***@gentlebath.com: High CPU usage of
Browser process in Chrome Task manager
https://code.google.com/p/chromium/issues/detail?id=141178

Problem - System tied us with multiple chrome.exe processes, hogs CPU and
fan roars.

Chrome Version: Version 38.0.2125.101 m
Sony Vaio Laptop Windows 7 Premium 64 bit OS, Service Pack 1
Extensions: AddThis, Gmail Enhancements, EverSync, Speed Dial & TamperMonkey

This happens at least two or three times in every 2 hours. Wireless
internet and GoogleDrive sync paused to see if that would help and it did
not. Attached screenshots of processes and CPU monitors while this was
happening.


Attachments:
Vaio-Chrome Issues.jpg 365 KB
Vaio-Chrome Issues #2.jpg 351 KB
Vaio-Chrome Issues #3.jpg 360 KB
--
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

[c***@googlecode.com]

Comment #70 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
https://code.google.com/p/chromium/issues/detail?id=141178

Just bought a new laptop and started to notice this problem. Once in a
while chrome just jumps to 20-30% CPU usage and stays there until i restart
the browser. In this state chrome is totally unusable on battery.

The task manager in chrome states that it is the browser process, not any
of the tabs or plugins. Attached a snapshot from the profiler page and a
process minidump from process explorer.

Attachments:
profile.json 5.4 MB
chrome.dmp 4.2 MB
--
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

[c***@googlecode.com]

Comment #73 on issue 141178 by ***@gmail.com: High CPU usage of
Browser process in Chrome Task manager
https://code.google.com/p/chromium/issues/detail?id=141178

If you're still having this problem, ETW traces are far more useful than
chrome://profiler or minidump data.

Bruce Dawson built a tool specifically for ETW tracing on Chrome:
https://randomascii.wordpress.com/2015/04/14/uiforetw-windows-performance-made-easier/
--
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

[c***@googlecode.com]

Updates:
Labels: Needs-Feedback

Comment #76 on issue 141178 by ***@chromium.org: High CPU usage of
Browser process in Chrome Task manager
https://code.google.com/p/chromium/issues/detail?id=141178

Uh, not sure why I got the bug, but I'd say get a trace:
https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs
--
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