QtWebEngine

I think I found the issue - it was because I the app uses a tray icon and WM_CLOSE doesn't fully close the app. This appears to play badly with the Windows restart manager. The solution was to use a custom script to terminate the app during update / removal.

@Hunglx Hello. Thank you very much for your information. I've understood that I need to switch to Qt 6.5, and set several attributes to QWebEngineProfile. I'll make a try. Thank you.

Any update on this issue?

@SGaist i will check it

@SGaist I have tried with qt 6 msvc 2019 but my website was slow again. Then I run my project in release mode. And it was all ok.

@tombalak not working

Hi, The first thing to do is to use a more recent version of Qt. The next possibility is to manually update Chromium and rebuild the QtWebEngine module with it. The last one is to use Qt 6 which has a more recent version of Chromium.

This unfortunately doesn't tell much more than 'it crashed', either. It's been a while that I've been working with WebEngine, and I'm also not sure which IDE you're using (is that VS Code)? Anyhow, the first thing you need is a proper stack trace, that tells you exactly which calls lead to the crash. This should be visible somewhere in your IDE after the crash when launching your app in debug mode. You can also try the tips at https://wiki.qt.io/QtWebEngine/ReportingCrashes .

Since you have it working now, please mark the thread as solved using the "Topic Tools" button or the three dotted menu beside the answer you deem correct so that other forum users may know a solution has been found :-)

@bloxorz I'm not sure but Fiddler should be able to capture anything from QtWebEngine if it runs Chromium. But nothing was recorded, and there were no certificate issues. I believe there is a safeguard or some mechanism that keeps Fiddler from capturing.