[Interest] QWebEngine makes QApplication ignore AA_UseOpenGLES

Agocs Laszlo laszlo.agocs at theqtcompany.com
Mon Jul 13 12:27:10 CEST 2015

Call QCoreApplication::setAttribute(Qt::AA_UseOpenGLES) before anything else, most importantly before constructing the Q(Gui)Application.

Right now you are making your request way too late, after WebEngine (and potentially others) have already run OpenGL related code.

Best regards,

From: interest-bounces+laszlo.agocs=theqtcompany.com at qt-project.org <interest-bounces+laszlo.agocs=theqtcompany.com at qt-project.org> on behalf of Allan Sandfeld Jensen <kde at carewolf.com>
Sent: Monday, July 13, 2015 11:56 AM
To: Shantanu Tushar
Cc: interest at qt-project.org
Subject: Re: [Interest] QWebEngine makes QApplication ignore AA_UseOpenGLES

On Monday 13 July 2015, Shantanu Tushar wrote:
> Hi,
> I tried passing that to the my app's executable (verified using process
> explorer that the cmdline argument was there), it still loads opengl
> instead of egl. The following gets passed to QtWebEngineProcess-
>  --type=renderer --enable-threaded-compositing --no-sandbox
> --use-gl=desktop --enable-deferred-image-decoding --lang=en-IN
> --device-scale-factor=1 --enable-delegated-renderer
> --enable-impl-side-painting --num-raster-threads=1
> --channel="4988.1.1687828899\2008412908" /prefetch:673131151
> Do I need to do something in my app code so that use-gl can be set to egl?
That looks odd. This means that when we ask Qt which OpenGL module is in use
it returns LibGL.

The method we use to get the use-gl flag is QOpenGLContext::openGLModuleType
which in turn asks QWindowsIntegration::openGLModuleType which does not check
the application flags.

You better open a bug report on it.

Interest mailing list
Interest at qt-project.org

More information about the Interest mailing list