|
|
The old switches like --disable-gpu or --use-gl=swiftshader causes that MM won't start at all.. And the new switches like --gl=egl-angle --angle=swiftshader --disable-gpu-compositing does not take any effect |
|
|
Checking now Chrome with and without HW acceleration settings and the only difference is the param --disable-gpu-compositing Nevertheless even with this param the GPU is still used in task manager (unlike in case of --disable-gpu in the past), more about the HW accelerated compositing: https://www.chromium.org/developers/design-documents/gpu-accelerated-compositing-in-chrome/ image.png (46,611 bytes) |
|
|
And here is the explanation why --disable-gpu-compositing does not completely disable GPU: image-2.png (65,035 bytes) |
|
|
So in build 3100 used the same param as Chrome (when 'Use graphics acceleration when available' is OFF) i.e. --disable-gpu-compositing |
- Anonymous
