The GPU process still runs with --disable-gpu

34,825 views
Skip to first unread message

PhistucK

unread,
Sep 1, 2012, 3:39:50 AM9/1/12
to Chromium-discuss
I am starting the canary using the following flags -
"C:\Users\me\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --disable-gpu --purge-memory-button --unlimited-quota-for-files --user-data-dir="c:\Personal\Temp\CleanProfileForDefaultApps" --flag-switches-begin --apps-new-install-bubble --conflicting-modules-check --enable-crxless-web-apps --enable-autologin --enable-css-regions --enable-devtools-experiments --enable-http-pipelining --enable-media-source --enable-nacl --enable-shadow-dom --enable-smooth-scrolling --enable-spdy3 --enable-style-scoped --enable-suggestions-ntp --enable-video-track --experimental-location-features --enable-experimental-extension-apis --disable-force-compositing-mode --enable-tab-groups-context-menu --flag-switches-end

I am using 23.0.1252.0 canary, on Windows Vista Home Premium SP 2 (Windows Classic theme).

But I can see still see the "GPU Process" in the Chrome task manager.
Do we care? Is this expected? Should I file an issue?


The reason for using this flag (off topic! but you can still read and comment ;)) -
I am using the --disable-gpu flag, because since Chrome 22 or Chrome 23, something has changed, I think it was related to using more of the GPU stuff and that causes my HP Pavilion dv4 to shut down its screen after a few minutes of using Chrome and never turn it on again (it seems like the system does not freeze). But I believe my computer is the one to blame, because it has serious hardware issues, like over heating and then suddenly hibernating whenever I do anything that involves too much (much is relative...) graphics like Flash, MapsGL, YouTube or even Heroes of Might and Magic III (a 1999 game), even when I cool it down using a full blown ventilator (while the air conditioner is on!)!



PhistucK

John Bauman

unread,
Sep 1, 2012, 10:14:50 AM9/1/12
to phis...@gmail.com, Chromium-discuss
You can check on about:gpu to be sure, but using that command-line option means that chrome won't use your GPU, but may still use the SwiftShader software rasterizer (inside the GPU process) to render 3D.


--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

PhistucK

unread,
Sep 1, 2012, 10:21:22 AM9/1/12
to John Bauman, Chromium-discuss
Thank you for replying.

What exactly do I need to see there in order to be sure?
That everything is in "Software only" mode?

Also, I remember seeing more than one GPU process (with --disable-gpu) simultaneously - does that make sense?

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
3D CSS: Software only, hardware acceleration unavailable
CSS Animation: Software only, hardware acceleration unavailable
WebGL: Software only, hardware acceleration unavailable
WebGL multisampling: Software only, hardware acceleration unavailable
Flash 3D: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Texture Sharing: Software only, hardware acceleration unavailable
Video Decode: Software only, hardware acceleration unavailable

PhistucK

John Bauman

unread,
Sep 1, 2012, 10:28:47 AM9/1/12
to PhistucK, Chromium-discuss
Everything's in software mode, so it sounds like it's working.

We start up a second, less-sandboxed GPU process when you visit about:gpu so we can grab more information about the GPU in your system. Nothing to worry about.

PhistucK

unread,
Sep 1, 2012, 10:30:50 AM9/1/12
to John Bauman, Chromium-discuss
Great, thank you very much for the prompt and detailed response!

PhistucK

robertcollier4

unread,
Nov 25, 2012, 11:08:58 AM11/25/12
to chromium...@chromium.org
You can completely disable the "GPU Process" with the following two switches:
 --disable-gpu --disable-software-rasterizer

Then the GPU Process won't start (and take up memory) at all.

--disable-gpu Disables GPU hardware acceleration. If software renderer is not in place, then the GPU process won't launch. 

Babak Mafakheri

unread,
May 26, 2013, 3:38:06 PM5/26/13
to chromium...@chromium.org
I can not add this comment " --disable-gpu --disable-software-rasterizer" at the end of target libe,
I see " the target box is not valid. Make sure the path and filename are valid.
What should I do to disable GPU process????
Reply all
Reply to author
Forward
0 new messages