PyQt6 v6.9.0 and Qt v6.9.0 available for testing
Charles
peacech at gmail.com
Sun Apr 6 14:51:11 BST 2025
I think this is a Windows specific bug based on this bug report:
https://bugreports.qt.io/browse/QTBUG-134746
On Sun, Apr 6, 2025 at 7:35 PM Florian Bruhin <me at the-compiler.org> wrote:
> Hey,
>
> On 2025-04-04T16:22:46 , Charles wrote:
> > My application using QtWebEngine (Windows 10, python 3.13) does not run
> > with Qt 6.9. Testing with various QSG_RHI_BACKEND values, only d3d12
> > doesn't crash but still results in a blank page. Setting
> > QSG_RHI_PREFER_SOFTWARE_RENDERER=1 works but results in slow page
> > scrolling. I don't think this is an issue of PyQt itself but most likely
> a
> > Qt issue.
> >
> > Test code:
> > [...]
> >
> > Console output:
> > [73696:94896:0404/162037.627:ERROR:shared_image_factory.cc(880)] Could
> not
> > find SharedImageBackingFactory with params: usage: Gles
> > 2Read|DisplayRead|DisplayWrite|Scanout, format: RGBA_8888,
> > share_between_threads: 0, gmb_type: empty, debug_label: QWE_SharedImage
> > Buffer
> > [73696:94896:0404/162037.627:ERROR:native_skia_output_device.cpp(253)]
> > CreateSharedImage failed.
> > [73696:94896:0404/162037.628:ERROR:raster_decoder.cc(1146)]
> > RasterDecoderImpl: Context lost during MakeCurrent.
> > [73696:94896:0404/162037.629:ERROR:raster_decoder.cc(1146)]
> > RasterDecoderImpl: Context lost during MakeCurrent.
> > [73696:94896:0404/162037.629:ERROR:raster_decoder.cc(1146)]
> > RasterDecoderImpl: Context lost during MakeCurrent.
> > [73696:94896:0404/162037.630:ERROR:raster_decoder.cc(1146)]
> > RasterDecoderImpl: Context lost during MakeCurrent.
> > [73696:94896:0404/162037.642:ERROR:shared_context_state.cc(885)] Failed
> to
> > make current since context is marked as lost
> >
> [73696:94896:0404/162037.643:ERROR:skia_output_surface_impl_on_gpu.cc(2264)]
> > Failed to make current.
> > [73696:94896:0404/162037.647:ERROR:shared_image_factory.cc(880)] Could
> not
> > find SharedImageBackingFactory with params: usage: Gles
> > 2Read|DisplayRead|DisplayWrite|Scanout, format: RGBA_8888,
> > share_between_threads: 0, gmb_type: empty, debug_label: QWE_SharedImage
> > Buffer
> > [73696:94896:0404/162037.649:ERROR:native_skia_output_device.cpp(253)]
> > CreateSharedImage failed.
> > [73696:94896:0404/162037.651:ERROR:raster_decoder.cc(1146)]
> > RasterDecoderImpl: Context lost during MakeCurrent.
> > [73696:94896:0404/162037.652:ERROR:raster_decoder.cc(1146)]
> > RasterDecoderImpl: Context lost during MakeCurrent.
> > [73696:94896:0404/162037.652:ERROR:raster_decoder.cc(1146)]
> > RasterDecoderImpl: Context lost during MakeCurrent.
> > [73696:94896:0404/162037.659:ERROR:shared_context_state.cc(885)] Failed
> to
> > make current since context is marked as lost
> >
> [73696:94896:0404/162037.659:ERROR:skia_output_surface_impl_on_gpu.cc(2264)]
> > Failed to make current.
>
> While the bug report seems to be Linux specific, the output looks very
> similar to this: https://bugreports.qt.io/browse/QTBUG-129769
>
> Possible fix here:
> https://codereview.qt-project.org/c/qt/qtwebengine/+/634920
>
> For what it's worth, I also got various reports about black rendering
> (only on X11?) and various artifacts (only Wayland?) for qutebrowser:
> https://github.com/qutebrowser/qutebrowser/issues/8535
>
> Florian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20250406/d970ee5b/attachment.htm>
More information about the PyQt
mailing list