https://bugs.kde.org/show_bug.cgi?id=434079

Marco Martin <notm...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/kirigami/commit/29da
                   |                            |bab2f536827bc1ecec63f5a0b0a
                   |                            |76f0809e5
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Marco Martin <notm...@gmail.com> ---
Git commit 29dabab2f536827bc1ecec63f5a0b0a76f0809e5 by Marco Martin, on behalf
of David Edmundson.
Committed on 09/03/2021 at 14:30.
Pushed by mart into branch 'master'.

Fix potential crash in SizeGroup

SizeGroup keeps a cache of a list of items, and when one updates does
calculations based on all items.

This list is stored as a list of QPointers as we don't explicitly track
deletion.

We have a list of items and guard for deletion, but they're QML owned.
So there's a point in time when it's pending deletion with the garbage
collector but the lower level object isn't managed by an engine.

As we go via QQmlProperty(item, QStringLiteral("Layout.preferredWidth"),
qmlContext(item)).write(maxWidth) this is problematic.

M  +4    -0    src/sizegroup.cpp

https://invent.kde.org/frameworks/kirigami/commit/29dabab2f536827bc1ecec63f5a0b0a76f0809e5

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to