https://bugs.kde.org/show_bug.cgi?id=375388
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@davidedmundson.co.uk
--- Comment #29 from David Edmundson <k...@davidedmundson.co.uk> ---
I have a theory on this.
The code is:
for (QQuickItem *childItem : qAsConst(childItems)) {
childVisibilityChanged |=
QQuickItemPrivate::get(childItem)->setEffectiveVisibleRecur(newEffectiveVisible);
}
...
emit q->visibleChanged();
which means if an item's visibility changing meant it ended up removing a
sibling, we've just altered a loop we're itterating over and we'd potentially
get the crash.
I tried reproducing that in a simple QML file but it didn't seem to make a
crash.
Though I'm a bit fuzzy on the new C++11 for loops and how they react.
--
You are receiving this mail because:
You are watching all bug changes.
