The QtWebView module comes to mind for that.

@KH-219Design glad to know I helped and thanks again for your input! After working perfectly during one full day of tests, the problem resurfaced again yesterday. Anything built in C++ using QWebEngineView works for all of my tests until it gets to one of the problem URLs, then abruptly crashes. No other URLs cause this problem and the page in question loads fine in any "real" browser I try it in. Since I'm not tied to any particular version of Qt, I've downgraded from Qt 5.14.2 to Qt 5.13.2. The Qt 5.13.2 QWebEngineView is not crashing. Also, it seems faster than Qt 5.14.2, and doesn't have another annoying behaviour which I believe to be graphics driver-related, which is that for certain pages of a well known UK based left wing newspaper the URL loads and then the whole web engine widget goes grey, and the program freezes. With no interest in faffing around further, I'm concluding that inside Qt 5.14.2, either the implementation of Chromium or the Qt WebEngine wrapper is buggy, at least for my particular combination of hardware and software. Original Problem Using MSVC 2017 + Qt 5.14.2, QWebEngineView crashes randomly on certain URLs which do not appear to be doing anything out of the ordinary. Solution Avoid Qt 5.14.2, or at least avoid the pre-built MSVC 2017 version which comes when you use the offline installer for Qt 5.14.2. In my case this meant downgrading to Qt 5.13.2.

hi vpettersson, i got the same errors and got it working with 3 symlinks: in sysroot/opt/vc/include/EGL mv egl.h egl.h-old mv eglext.h eglext.h-old mv eglplatform.h eglplatform.h-old ln -s /home/jw78/raspi/qt-everywhere-src-5.15.2/qtwebengine/src/3rdparty/chromium/third_party/khronos/EGL/eglext.h eglext.h ln -s /home/jw78/raspi/qt-everywhere-src-5.15.2/qtwebengine/src/3rdparty/chromium/third_party/khronos/EGL/egl.h egl.h ln -s /home/jw78/raspi/qt-everywhere-src-5.15.2/qtwebengine/src/3rdparty/chromium/third_party/khronos/EGL/eglplatform.h eglplatform.h of course you must adjust your paths (/home/jw78/raspi/qt-everywhere-src-5.15.2) there are many egl.h/eglext.h/eglplatform.h to include and because of the include order the comiler fetches first the files in sysroot/opt/vc/include/EGL probably the better solution is to reorder the "-I" flags for the compiler, but i have no idea how to do this i did not dpkg --purge libraspberrypi-dev

@jsulm http://download.qt.io/official_releases/qt/5.12/5.12.8/single/qt-everywhere-src-5.12.8.tar.xz i downloaded it form here and followed this steps https://www.tal.org/tutorials/building-qt-512-raspberry-pi according to that i can say that 3rd party content also built along with the code

hi wish this help https://forum.qt.io/topic/117637/easy-way-to-cross-compile-qt-for-raspberry-pi

The following command fixed. sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

It's a QT bug ( https://bugreports.qt.io/browse/QTBUG-79254 ) If somebody every needs it again I implemented a workaround which I posted here: https://stackoverflow.com/questions/62152845/touch-freeze-in-qtwebengine-after-opening-a-dropdown-menu

Great ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :-) In case, there's an answer that provides the correct hint, you can also use the three button menu to mark it as the correct answer.

@forca maybe you need to do some additional steps From QSslSocket documentation: Describes the peer verification modes for QSslSocket. The default mode is AutoVerifyPeer, which selects an appropriate mode depending on the socket's QSocket::SslMode. QSslSocket::QueryPeer 1 QSslSocket will request a certificate from the peer, but does not require this certificate to be valid. This is useful when you want to display peer certificate details to the user without affecting the actual SSL handshake. This mode is the default for servers. Note: In Schannel this value acts the same as VerifyNone. And looking at this QWebEnginePage browser example, check the Downloading Favicons code snippet, which may help you accessing the underlying QSslSocket

@hsynkrkmz From posts I have seen elsewhere: this happens with QtWebEngine, sometimes. It seems to very picky about where it gets destroyed. If you are waiting for definitive answer, you might like to try moving around where/how you destroy it and see if different behaviour.

@Yakov-Eremin read this: https://doc.qt.io/qt-5/qtwebengine-features.html#html5-geolocation to check if geoclue is working properly simply test if it delivers a position: https://doc.qt.io/qt-5/qml-qtpositioning-positionsource.html#example-usage

Does the app work if you start it with --single-process added to the command line?

I've got the same situation on my iMX6 with Yocto Rocko. Any solution for this issue? Is the same situation on new release Sumo or Thud?

I use Windows and msvc 2015 compiler. I Installed a qt-opensource-windows-x86-5.9.2.exe. Then I changed a very little some headers in qtwebengine module. Then, I need to rebuild it. I opened configurated by Qt console for msvc2015 x86_64 compiler, go to the src/qtwebengine, typing qmake and after that nmake. nmake only outputs Microsoft (R) Program Maintenance Utility Version 14.00.24210.0 Copyright (C) Microsoft Corporation. All rights reserved. but did nothing. I downloaded qtwebengine-opensource-src-5.9.2 separately and try to buid it - the same result. How to rebuild qtwebengine using msvc 2015 compiler?

Hi, From a quick look at the sources of the module: Yes it does and yes for iOS and Android, so in your case for macOS, no. In 5.9, the native macOS web view is used rather than QtWebEngine and support for winrt For number 2, what should your application do ?

Nowadays the software renderer for WebGL works fine. I wonder if there is some easy way to detect if the video adapter is affected (probably intel && being "old") and if that's the case, to switch to software renderer, at run-time - maybe before initializing QApplication? in order to pass --enable-webgl-software-rendering parameter programmatically.

Hi, Thanks for replying, I solved my issue. I was missing some "#include" in different files.

@mpergand you are right, this line solved the problem. Thank you very much!

@jsulm Thanks for the suggestion. I forget about ldd and usually notice about missing dependencies when I get an error. It's a great suggestion in this case when I may not see the errors, but I checked and all dependencies have been met. @sneubert You're the bomb!!! That was it. I recompiled with the enable plugins flag set and all is working now. Thank you so much for your help. Not sure how else I would have found it.

Looks like adding the use_proprietary_codecs define in .qmake.conf is not allowed by design?, i need to add these changes in order qt 5.8 to pick up the additional WEBENGINE_CONFIG : #Edit ..\qt-everywhere-opensource-src-5.8.1\qtwebengine\.qmake.conf #Add WEBENGINE_CONFIG += use_proprietary_codecs #Edit ..C:\QT-Build\qt-everywhere-opensource-src-5.8.1\qtwebengine\configure.json #Line 45 "autoDetect": false, into "autoDetect": true,

mark qtwebengine_resources.pak + qtwebengine_resources_100p.pak+ qtwebengine_resources_200p.pak

In my case this function works: onFeaturePermissionRequested: { console.log("onFeaturePermissionRequested"); webEngineView.grantFeaturePermission(securityOrigin, feature, true); } Tested on Qt 5.6 and Qt 5.7 on Desktop and Embedded

Hi, Did you also install Qt for MSVC2013 ?

Hi and welcome to devnet, That's a question you should bring to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

Hi, I'd recommend posting that question to the the QtWebEngine mailing list. You'll find there QtWebEngine's developers/maintainers. This forum is more user oriented.

Thanks. I take a look at hat and at http://tishion.github.io/QCefView/ But then we end up in using an extra lib. Something we want to avoid.... :-(