QtWebEngine

I found the issue. When I migrated to the new QT Visual Studio tools upon being prompted by VS (I'm upgrading from Qt 5.15.0), this section was added to a higher level .props file where it was not previously. <PropertyGroup Label="QtSettings"> <QtInstall>Qt_Qt-6.9.0</QtInstall> <QtModules>core;gui;network;widgets;webenginecore</QtModules> </PropertyGroup> Deleting the "network" and "webenginecore" items got the webenginecore error to disappear.

Hello, Thank you for your answer. Just to keep you informed: at the same time I was writing here, another user also raised the issue to RiverBanks (https://www.riverbankcomputing.com/pipermail/pyqt/2025-May/046232.html), so I didn't post. The issue then bounced back to Qt: https://bugreports.qt.io/browse/QTBUG-136637 I confirm problem occurs also with PySide6.

Looks like this is going to be fixed in Qt 6.9.1, related patch - https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/634034

I've reported this issue as a bug at: https://bugreports.qt.io/browse/QTBUG-136652

Do we have a solution for this?

@DJBob-Gaming Is this spam? Does not sound like any answer to the question.

@Victorusik said in About version of QtWebEngine: And what does "debug information files" mean Those are debug files for Qt. You need them if you want to debug into Qt code (to see what happens inside Qt code).

@JKSH Thanks a lot for your answer!!! This question bugged me for days.

Does anyone know if the 32bit compilation of QtWebengine requires the 64bit versions of python2 and Node.js?

Additional thing: before start I set environment variable QTWEBENGINE_DISABLE_SANDBOX=1.

Hi and welcome to devnet, They might be using proprietary codecs, in which case you need to build Qt WebEngine with them enabled. See here.

did you able to fix the issue?

Very embarassing but I found out I have to to build in RELEASE mode to have the full GPU acceleration. In practice that means doing cmake -DCMAKE_BUILD_TYPE=Release .. Then run windeployqt again. There should be QWebEngineProcess.exe - if there is QWebEngineProcessd.exe (the d for "debug") that means it is still in debug mode and will be slow.

Thanks for your answer. In my case, I've tested WebEngine Quick Nano Browser example using Qt 6.4.3. It uses QGuiApplication and QtWebEngineQuick::initialize is called before creating the application instance. If I move QtWebEngine::initialize() below QGuiApplication, I not only get the same warnings but also an additional message: QtWebEngineQuick::initialize() called with QCoreApplication object already created and should be called before. This is deprecated and may fail in the future. I like to take care of warnings whenever possible, as they can indicate potential issues. Is there any official explanation for these specific warnings?

Problem solved : it is necessary to change active console code page to utf-8 with chcp 65001 command.