Unsolved page failure in webkit start
-
Hi,
I'm experiencing a failure deep in webkit right at the start of the application on Windows 10.
This is an existing, large app, developed up until now on windows 7 and deploying qt 5.5.1. My colleagues, still using these settings, do not encounter this issue. We all use Visual Studio 2010.
A short output of the failure follows:
ASSERTION FAILED: guardPage.Protect & PAGE_GUARD
wtf\StackBounds.cpp(207) : WTF::StackBounds::initialize
I stress that my colleagues still working on Windows7 do not see this issue.
Has anyone encountered anything similar?
Thanks for the feedback.
V. -
Hi
Just to be 100% sure. If your colleague creates a version on win 7.
and you then run this exact version on win 10 , does it still assert?
Im not talking about compile your own.Running his, produce this ASSERT fail?
-
@mrjj I'll have to check on that, at the moment we work with our own, self-compiled versions. Thanks.
-
@Vieira
Hi, super.
Im asking - as if his exe -also- fails
then its clearly win 10 + Qt 5.5 thing + webkit thing. -
@mrjj Thanks for your feedback.
My colleagues executables run fine on my system (only release mode tested), compiled with visualstudio 2010 on their system, windows 7, deploying qt 5.5.
On my system (windows 10), my code crashes both in debug and release mode.
Any ideas on how to fix this for Windows 10? Thanks again.
-
@Vieira
Well, first i would try to find out if this issue is on
all windows 10 or just this one.
So would it be possible to install win 10 on virtual machine and try fresh compile there or some other
win 10 that is not your system?Clearly compiling it on win 10, does something to it. Might be a Visual Studio thing or
Qt 5.5 not really 100% happy for win 10 when using webkit.So would be great to know if this happens on all win 10 before we try to find out what it could be. :)
-
On my system (windows 10), my code crashes both in debug and release mode.
Did you ever install any other version of Qt ? (on this system)
besides the 5.5? -
@mrjj Thanks a lot for your feedback.
I understand your points. For the moment it is difficult to test this on another win10 system as this the only one have available at the moment. Virtualisation is an option but there are a couple of organisational issues regarding that (read: IT policies).
Regarding the Qt version, would you think that upgrading to a higher version could possibly solve this issue on Windows 10?
-
@Vieira
Ok. its also a bit time consuming installing VS also :)Regarding the Qt version, would you think that upgrading to a higher version could possibly solve this issue on Windows 10?
Yes. But webkit might not be directly supported as there is new QWebEngine., so you might need to compile it yourself for above Qt5.5 so might not be super easy to test.
Do u think its possible to make small sample that crash same way?
-
-
@Vieira
Well hopefully its just your win 10. :)
Please do report back.Also, if you can make small sample, i can run it in win 10 to test.