WebEngineView performance issues vs. native Chrome

jars121

Hi all,

I'm testing a WebEngineView implementation at the moment, which isn't working quite as intended. I've got a model-viewer instance running in my WebEngineView, which exhibits quite a low framerate (ghosting and stuttering when rotating the 3D model) and intermittent tearing and flickering.

I've enabled a remote debugging window (via QTWEBENGINE_REMOTE_DEBUGGING), which allows me to view the WebEngineView content in an external Chrome window at the same time as the WebEngineView content in my application. What I'm finding is that the external Chrome debugging window is infinitely better than the WebEngineView content in my QtQuick application. It has a natively high framerate, absolutely no ghosting, stuttering, tearing or flickering.

I've tried every possibly combination of QTWEBENGINE_CHROMIUM_FLAGS I can think of, including various rasterization options, GPU vsync, hardware overlays, forced compositing, WebGL2, etc. but nothing seems to make a difference.

Is it expected behaviour that the performance inside a WebEngineView will be noticeably worse than the same content in an external browser window? If so, am I better off ditching WebEngineView and instead instantiating an external Chrome instance in the application as a foreign window?

I'm using Qt 6.8.0 on Windows 11, with the latest Nvidia drivers on a 4090.

Thanks!

jars121

GGnome provided the solution to this problem in this thread.

Setting the following in my main.cpp before initialising the app cured all performance issues with my WebEngineView:

QQuickWindow::setGraphicsApi(QSGRendererInterface::OpenGL);