Enable hardware acceleration with QtWebEngine #2671
Comments
|
This is done by Qt, there's nothing qutebrowser can do about it. I've heard some talk about the investigating what more they can do with how they render stuff, but I'm not sure what the state there is - I also didn't find an issue in their tracker so far. |
|
@wesbarnett Thanks for this finding! |
|
Note that there's probably a good reason that Chromium and Qt have those switches/blacklists. |
|
Any (recent) information on this? Is it still not recommended to use those flags, and what might be reasons for auto disabling them? |
|
Rijnder Wever writes:
Any (recent) information on this? Is it still not recommended to use those flags, and what might be reasons for auto disabling them?
For me, this causes CPU spikes and stutters when typing on some websites. I
don't think hw acceleration matters too much though, especially if you play
video in a competent player.
|
|
Agreed, but I had to switch to viewing some videos in my browser because of some DRM stuff that was recently enforced. |
|
@rien333 Not really, you'd need to ask the Chromium devs. |
I have a project with QT/VS2017/Win10 - where i try put this parameter ? Where i make a list situation ? |
|
@gitjanfri You mean you are running qutebrowser from visual studio? Presumably like this. If you are making some other QtWebengine based project you pass, for example, "--ignore-gpu-blacklist" in a list as the argument to the constructor of QApplication. |
There is a discussion of these flags in qutebrowser's bugtracker (not otter!), qutebrowser/qutebrowser#2671 but the mechanism of "--qt-flag" is specific to qutebrowser: it isn't a general Qt thing. I can't find anywhere in otter-browser's source history where it has a --disable-gpu flag: that **is** a Qt thing, as documented at https://doc.qt.io/qt-5/qtwebengine-debugging.html However the application has to be able to pass that on to Qt (which otter apparently doesn't anymore, and neither does falkon). Overall the recommendation is to use environment variables to manage Chromium-inside-WebEngine, as documented by Qt, e.g. QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" otter-browser PR: 237277 240097 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@542576 35697150-7ecd-e111-bb59-0022644237b5
There is a discussion of these flags in qutebrowser's bugtracker (not otter!), qutebrowser/qutebrowser#2671 but the mechanism of "--qt-flag" is specific to qutebrowser: it isn't a general Qt thing. I can't find anywhere in otter-browser's source history where it has a --disable-gpu flag: that **is** a Qt thing, as documented at https://doc.qt.io/qt-5/qtwebengine-debugging.html However the application has to be able to pass that on to Qt (which otter apparently doesn't anymore, and neither does falkon). Overall the recommendation is to use environment variables to manage Chromium-inside-WebEngine, as documented by Qt, e.g. QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" otter-browser PR: 237277 240097
There is a discussion of these flags in qutebrowser's bugtracker (not otter!), qutebrowser/qutebrowser#2671 but the mechanism of "--qt-flag" is specific to qutebrowser: it isn't a general Qt thing. I can't find anywhere in otter-browser's source history where it has a --disable-gpu flag: that **is** a Qt thing, as documented at https://doc.qt.io/qt-5/qtwebengine-debugging.html However the application has to be able to pass that on to Qt (which otter apparently doesn't anymore, and neither does falkon). Overall the recommendation is to use environment variables to manage Chromium-inside-WebEngine, as documented by Qt, e.g. QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" otter-browser PR: 237277 240097 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@542576 35697150-7ecd-e111-bb59-0022644237b5
|
Relevant upstream bug: https://bugreports.qt.io/browse/QTBUG-91677 |
There is a discussion of these flags in qutebrowser's bugtracker (not otter!), qutebrowser/qutebrowser#2671 but the mechanism of "--qt-flag" is specific to qutebrowser: it isn't a general Qt thing. I can't find anywhere in otter-browser's source history where it has a --disable-gpu flag: that **is** a Qt thing, as documented at https://doc.qt.io/qt-5/qtwebengine-debugging.html However the application has to be able to pass that on to Qt (which otter apparently doesn't anymore, and neither does falkon). Overall the recommendation is to use environment variables to manage Chromium-inside-WebEngine, as documented by Qt, e.g. QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" otter-browser PR: 237277 240097
Is it possible to enable the hardware acceleration with QtWebEngine in some way?
I could access
chrome://gpu/where it says it is not enabled. I read that for Chromium you can enable these kind of options underchrome://flags/but inside qutebrowser we don't have such a page, is it possible to do somehow with set or some other way?The text was updated successfully, but these errors were encountered: