diff options
author | apatrick@chromium.org <apatrick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-01 20:09:24 +0000 |
---|---|---|
committer | apatrick@chromium.org <apatrick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-01 20:09:24 +0000 |
commit | 981c1c5d6f46c1435bbcf466e35a8aa047a367a9 (patch) | |
tree | 6fa889c4075ca978cf194703c9640c0ffc8677a1 /gears/SConscript.libjpeg | |
parent | 38f57abb36fa6c91d9939a2393f9998dd40c51ba (diff) | |
download | chromium_src-981c1c5d6f46c1435bbcf466e35a8aa047a367a9.zip chromium_src-981c1c5d6f46c1435bbcf466e35a8aa047a367a9.tar.gz chromium_src-981c1c5d6f46c1435bbcf466e35a8aa047a367a9.tar.bz2 |
Switched GPU watchdog timeout to be based on main thread's user + kernel time rather than wall clock time on Windows.
Only on Windows because it is the only platform 58396 appears to be happening on. My latest hairbrained theory is that it is timing out and aborting while Windows boxes are resuming from hypernation. In that case wall clock time might incorporate a lot of I/O time for paging in data from swapfile. This is an attempt to hide that I/O time, counting only active CPU time.
It catches hangs like this:
for (;;) {
}
and this:
for (;;) {
Sleep(0);
}
but not this:
for (;;) {
Sleep(1000);
}
because that just makes the thread largely idle. It also does not catch deadlocks.
Also fixed null dereference in GPU watchdog termination code.
BUG=64648, 58396
TEST=test GPU watchdog locally, try
Review URL: http://codereview.chromium.org/5301007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67891 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'gears/SConscript.libjpeg')
0 files changed, 0 insertions, 0 deletions