I've been digging around for the last couple of days trying to find the root cause of the issue and then it turned out that even the simplest Qt Quick application will crash with the same stack trace as long as it displays some text. Likewise none of the examples that are shipped with Qt (accessible through the Welcome -> Examples screen in Qt Creator) work, they simply crash on startup.
Would it be safe to assume it's a bug with Qt 5.9.1 built using MSVS 2017 (VC14.1)?
How do I even proceed now? Do I report it on the issue tracker?
Hi, googling finds many with the same problem, for example here
Just guessing, but perhaps you could try some of the suggestions in there...
Thanks for the link.
It seems this issue doesn't even solved in Stack Overflow :(
Any way, I did some of the suggestions mentioned in it.
Installed all redistributable package of x86 (cuz I built my app using Qt mingw53_32) for 2012 - 2013 - 2015 - 2017 (I tested my app after each vcredist)
Installed all redistributable package of x64 for 2012 - 2013 - 2015 - 2017 (I tested my app after each vcredist)
Nothing changed still see my app crashes without any logical reason!
Now I'm very sad because I can run my app only if I installed Qt on my machine which is impractical solution for deploying my app.
Then, AFAUI, you have all what you need to continue. If implementing the proxy model looks daunting start by just a custom QAbstractItemModel with a QListView and once you have what you want you can go with the proxy and the shifting I suggested before.
Right, the library doesn't seem to be very Windows friendly. It assumes the pointers to GL functions resolved and available in global scope, which is not how it usually works on this platform. Moreover it seems to force ANGLE and OpenGL ES (or at least tries to) on Windows in the .pri file, but then is inconsistent in how it checks for that.
I'd say contact the authors and ask them to fix the Windows parts.
AFAIK, the recent version of the QtWebView module uses the QtWebEngine module for Windows. Module that is not available for MinGW currently. Also you are are using a relatively old version of Qt so first thing you should update if possible to at least 5.8.
I found that your steps also worked in my case, but I also installed the Universal CRT: KB2999226. That is because the Windows 10 SDK mentioned that non-Windows 10 platforms must install the Universal CRT. I installed Qt 5.8.0 on a Windows 7 platform.
A little more info after starting a 2nd debug session.
I set a breakpoint so that I could walk through the first call to QAbstractItemView::event -> QAbstractScrollArea::event -> QPainter::QPainter -> QPainter::begin
The first call to redirected has the redirectedDev pointer in the QPaintDevice pointing to a valid QPaintDevice with a QImage, 7 slots in the __vfptr that look valid, and both the painters and reserved member variables set to 0 (zero):
The overlapped mode is the problem. If you only have a handle then ReadFile / WriteFile will fail if you don't include the overlapped structure in the call. It was opened with the OVERLAPPED flag so this parameter cannot be NULL.
What exactly are you trying to do? Maybe there is another way.
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.