Details
-
Bug
-
Resolution: Incomplete
-
P2: Important
-
None
-
5.12.4
-
None
-
Windows 7 64Bit (Application also running in 64 Bit)
-
Windows
Description
Captured these errors from a user log file:
CRITICAL:Qt:Unknown:ARB::createContext: wglCreateContextAttribsARB() failed (GL error code: 0x500) for format: QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile), shared context: 0x30000 (Der Vorgang wurde erfolgreich beendet.) CRITICAL:Qt:Unknown:GDI::createContext: wglShareLists() failed. (Unknown error 0xc00710dd.) CRITICAL:Qt:Unknown:ARB::createContext: wglCreateContextAttribsARB() failed (GL error code: 0x500) for format: QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize 8, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile), shared context: 0x30000 (Der Vorgang wurde erfolgreich beendet.) CRITICAL:Qt:Unknown:GDI::createContext: wglShareLists() failed. (Unknown error 0xc00710dd.)
The behaviour that failed is that some WebEngine-powered windows had blank either white or black visuals.
The system in question has Windows 7 with Intel HD Graphics 4600. We updated their graphics driver for them manually and the issue "appears" gone for now.
We likely have quite a few more users out there with an old driver and currently we have 5.12.1 out there and this user was beta testing the new update that would change it over to 5.12.4. We're afraid that a rollout of this update would create this issue for hundreds of users should we release it. Due to other unrelated issues we already could not update to 5.13.0, 5.12.2 or 5.12.3, as they respectively broke other critical components.
Update: The Graphics Update broke it entirely and now the user gets this:
Rolling back to our stable version works fine, but it looks like we continue to be stuck on 5.12.1
