[qt/qt/qtdeclarative]: Summary of bulk changes made

Git repository change summary for qt/qt/qtdeclarative
Pushed by mirror-service into branch '6.11'.
Changed from eb9e604728185ddc814f75658222e385dd4c8050 to 3af5f468d368bc462fe75af9dc855ac9756d4695
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit 740118cb8cc4eaf01d0991da0ab1bf892cbbc58e by Qt Cherry-pick Bot (on behalf of Tor Arne Vestbø) on 15/08/2026 at 17:00..
WindowContainer: Disconnect our own connections when destructing

We disconnect in the destructor to avoid callbacks into a window
container that's no longer one. QObject drops the connections for us,
but not until ~QObject, and ~QQuickItem emits windowChanged before
that. Signals dispatch straight to the slot, not via the vtable, so we
would end up in parentWindowChanged with the QQuickWindowContainer part
of the object already gone.

The disconnect(this) we used for this was both too blunt and too
narrow. It removed every connection where we were both the sender and
the receiver, including ones made by others, such as the destroyed()
connection QTestAccessibility uses to track the objects of the
accessibility events it records. And it left the contained window
connected, so we still reacted to its signals, and to its events via
our event filter, as we destroyed it right below.

We now disconnect exactly what we connected ourselves, and reset the
window pointer, which windowDestroyed() used to take care of.

Pick-to: 6.8
Change-Id: I527e41c2b26cc8a4f5835bd81820e7ba86cc002c
Reviewed-by: Morten Johan Sørvig <[email protected]>
Reviewed-by: Mitch Curtis <[email protected]>
(cherry picked from commit 0809c47f01f2aa19de174c1983d99b5befce2633)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
(cherry picked from commit 03ce5822a1621c0ee2699740319e7617851614b0)
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/740118cb8cc4eaf01d0991da0ab1bf892cbbc58e

Git commit 3af5f468d368bc462fe75af9dc855ac9756d4695 by Qt Cherry-pick Bot (on behalf of Eirik Aavitsland) on 15/08/2026 at 17:00..
Fix potential crash in GeometryRenderer for async shapes

In certain cases there was a race condition where the finishing
signals from the fill and stroke worker threads could cross the
deletion of the renderer, leading to a crash during delivery. Fix by
inserting a queued connection between, so that the signals are emitted
in the same thread where the renderer lives.

Fixes: QTBUG-148532
Pick-to: 6.8
Change-Id: Ia24580cc0e6bece7db37deb09e663749d6897a9a
Reviewed-by: Laszlo Agocs <[email protected]>
(cherry picked from commit 400b2bc4c7c29e75be56d09c715aef3a01c6a667)
Reviewed-by: Qt Cherry-pick Bot <[email protected]>
(cherry picked from commit 002abbc1ab33ee2e566c81fed31b7fdedcbb6067)
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/3af5f468d368bc462fe75af9dc855ac9756d4695