Commit 1c9cf51b authored by Erik Chen's avatar Erik Chen Committed by Commit Bot

Increase DevTools SystemInfoGPU timeout for Windows.

Before this CL, DevTools would crash the browser if it did not get a response in
5 seconds. This timeout is too low for Windows. On Catapult perf tests on
Windows, it takes ~3 seconds for the GPU process to respond on average, and
sometimes it takes more than 5 seconds.

Bug: 873112
Change-Id: I67ee82a1a75df0ba9e1b483a58c66c56a8bf2213
Reviewed-on: https://chromium-review.googlesource.com/1170584Reviewed-by: default avatarKenneth Russell <kbr@chromium.org>
Reviewed-by: default avatarAndrey Kosyakov <caseq@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582375}
parent 1ccd841a
...@@ -33,7 +33,8 @@ using GetInfoCallback = SystemInfo::Backend::GetInfoCallback; ...@@ -33,7 +33,8 @@ using GetInfoCallback = SystemInfo::Backend::GetInfoCallback;
// Give the GPU process a few seconds to provide GPU info. // Give the GPU process a few seconds to provide GPU info.
// Linux Debug builds need more time -- see Issue 796437. // Linux Debug builds need more time -- see Issue 796437.
#if defined(OS_LINUX) && !defined(NDEBUG) // Windows builds need more time -- see Issue 873112.
#if (defined(OS_LINUX) && !defined(NDEBUG)) || defined(OS_WIN)
const int kGPUInfoWatchdogTimeoutMs = 20000; const int kGPUInfoWatchdogTimeoutMs = 20000;
#else #else
const int kGPUInfoWatchdogTimeoutMs = 5000; const int kGPUInfoWatchdogTimeoutMs = 5000;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment