https://bugs.kde.org/show_bug.cgi?id=468180
Fushan Wen <qydwhotm...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version Fixed In|Qt 6.6 |5.27.7
Resolution|UPSTREAM |FIXED
Latest Commit|https://invent.kde.org/qt/q |https://invent.kde.org/plas
|t/qtdeclarative/-/commit/8a |ma/plasma-workspace/-/commi
|74155411d7a22bb8efa405fe59a |t/b61ef42d83cfc27cd0d70a55c
|681e47e6b45 |309163571e69e84
--- Comment #12 from Fushan Wen <qydwhotm...@gmail.com> ---
Git commit b61ef42d83cfc27cd0d70a55c309163571e69e84 by Fushan Wen.
Committed on 17/07/2023 at 13:45.
Pushed by fusionfuture into branch 'Plasma/5.27'.
applets/notifications: add workaround for QTBUG-100392
Citing the bugreport:
```
Qt/QML crashes at runtime when an animation is started for the second time
after caching its targets' properties, but one or more of those targets are
actually destroyed by the time it restarts.
It is likely because the list<> property type does not emit any on*Changed()
signal when any of its items are destroyed — either manually by invoking
QtObject::destroy() method, by an Instantiator when it removes its managed
objects, or in any other way. Lists start showing null values after control
returns to the even loop (so that Qt finishes actually destroying an object and
cleans up all references it can find), but according to the backtrace Animation
does some property caching, and so it tries to access freed memory leading to
Segmentation fault.
```
Ref: https://bugreports.qt.io/browse/QTBUG-100392
Ref:
https://invent.kde.org/qt/qt/qtdeclarative/-/commit/8a74155411d7a22bb8efa405fe59a681e47e6b45
FIXED-IN: 5.27.7
M +13 -5
applets/notifications/package/contents/ui/CompactRepresentation.qml
https://invent.kde.org/plasma/plasma-workspace/-/commit/b61ef42d83cfc27cd0d70a55c309163571e69e84
--
You are receiving this mail because:
You are watching all bug changes.
