summaryrefslogtreecommitdiff
path: root/chromium/content/browser/gpu/gpu_process_host.cc
diff options
context:
space:
mode:
authorPeter Varga <pvarga@inf.u-szeged.hu>2017-08-10 11:37:05 +0200
committerAllan Sandfeld Jensen <allan.jensen@qt.io>2017-08-10 10:34:16 +0000
commit653d19d26000d016fc915444c8323a5fe96de18a (patch)
tree0e2e965db27d344b6336cb4cf89b2ec07604d441 /chromium/content/browser/gpu/gpu_process_host.cc
parentc1448e447d49d5ba6578fbd614b5f895753dc7f4 (diff)
downloadqtwebengine-chromium-653d19d26000d016fc915444c8323a5fe96de18a.tar.gz
Fix Renderer and GPU threads on windows
These threads are using the UI message loop on Windows per default. This won't work since the UI message loop is handled by Qt and the Renderer and GPU threads won't work with it properly. Force these threads for using the default message loop as they use it on Linux platform. Change-Id: I8b04ba9070912378cf1d13173ddff48e98f9a49b Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Diffstat (limited to 'chromium/content/browser/gpu/gpu_process_host.cc')
-rw-r--r--chromium/content/browser/gpu/gpu_process_host.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/chromium/content/browser/gpu/gpu_process_host.cc b/chromium/content/browser/gpu/gpu_process_host.cc
index 6b0b7066af7..5bc1f1d6c89 100644
--- a/chromium/content/browser/gpu/gpu_process_host.cc
+++ b/chromium/content/browser/gpu/gpu_process_host.cc
@@ -622,7 +622,7 @@ bool GpuProcessHost::Init() {
process_->GetInProcessBrokerClientInvitation(),
process_->child_connection()->service_token())));
base::Thread::Options options;
-#if defined(OS_WIN)
+#if defined(OS_WIN) && !defined(TOOLKIT_QT)
// WGL needs to create its own window and pump messages on it.
options.message_loop_type = base::MessageLoop::TYPE_UI;
#endif