summaryrefslogtreecommitdiff
path: root/chromium/base/task/promise/promise_value.h
diff options
context:
space:
mode:
authorJüri Valdmann <juri.valdmann@qt.io>2020-02-10 14:05:06 +0100
committerAllan Sandfeld Jensen <allan.jensen@qt.io>2020-02-11 12:38:23 +0100
commitc3dcc07f4f3f94ed510dc4bc646e0a897cc57860 (patch)
tree3133447902210156cf194d1c5d545c1c52f2c34a /chromium/base/task/promise/promise_value.h
parentd6d89a179a397c09aaf98e966b95ec7dabd28626 (diff)
downloadqtwebengine-chromium-c3dcc07f4f3f94ed510dc4bc646e0a897cc57860.tar.gz
Don't force gpu process launch on macOS with vizdc and no GL
Turns out Chromium on macOS expects vizdc to run inside the GPU process. In fact, Chromium attempts to launch a GPU process even with --disable-gpu, because GpuDataManager::GpuProcessStartAllowed returns true whenever vizdc is enabled. Change-Id: I2f31ad8accfb418446fc242ed00ebf1f6accd6fd Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Diffstat (limited to 'chromium/base/task/promise/promise_value.h')
0 files changed, 0 insertions, 0 deletions