QtWebEngine

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.

@JonB said in Optimization tips for QT WebEngine and/or Chromium?: Is there any solution for the performance problem in debug? As I see, it works smooth in release, but in debug the performance is very poor. I am using Qt6.5.2 and using QWebEngineView in my cpp application to run a parallel web gui alternative of our current desktop solution. win10 enterprise 19045 i7-10850h turbo 32gb ram

This is Similar Issue like mine just refer this. https://bugreports.qt.io/browse/QTBUG-134278

Solved this issue by Disabling the sandbox . Added this in main.cpp: // Disable the sandbox before initializing QtWebEngine qputenv("QTWEBENGINE_DISABLE_SANDBOX", "1"); Disabling the sandbox allows the content to display successfully.

@MonkeyBusiness If you use normal resources (not external resources) then there is no need for this because the resources will be part of the executable file. You also did not answer any of the latest questions...

I will try that. Thank you.

@jsulm Per the link, which is a screen shot of the --help, it just lists all the possible extra libraries at the end and it states Qt libraries can be added by passing their name (-xml) which is why I thought maybe it should be a single hyphen?

Seems to be the same topic like: https://forum.qt.io/topic/156752/qt6-7-compile-failed-from-source-in-windows11/3

If I comment below lines in component which is handling Webengine and browser related logic, the issue is not observed. QWebEngineProfile *m_profile; m_profile- >clearHttpCache(); Any idea if we need to change above to logic in QT5.15.11 for better handling. As currently it seems call is hang/stuck if i keep it.

Thank you, it seems to be the case. Do you happen to know how to set this attribute in QML? I need to modify part of extension (plasmoid) for KDE Plasma, it uses QML to setup the WebView.

@Mallikarjuna said in QT Webengine bitbake do_compile error for QT6.8.1: ../../../../../git/src/3rdparty/chromium/third_party/distributed_point_functions/code/dpf/internal/evaluate_prg_hwy.cc:152:14: internal compiler error: in eliminate_stmt, at tree-ssa-sccvn.cc:6870 You get an internal compiler error when compiling Chromium. You could try to get newer compiler or build different Chromium version.