https://bugs.kde.org/show_bug.cgi?id=357435
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |k...@davidedmundson.co.uk
--- Comment #5 from David Edmundson <k...@davidedmundson.co.uk> ---
http://doc.qt.io/qt-5/qtquick-performance.html
Note: A pattern which is tempting, but should never be used, is creating your
own QEventLoop or calling QCoreApplication::processEvents() in order to avoid
blocking within a C++ code block invoked from QML. This is dangerous, because
when an event loop is entered in a signal handler or binding, the QML engine
continues to run other bindings, animations, transitions, etc. Those bindings
can then cause side effects which, for example, destroy the hierarchy
containing your event loop.
--
You'd think it should be safe if you launch it from a queued connection so that
the heirachy doesn't contain anything on the QML side.. however we still got
crashes when kickoff did that. Didn't really understand that.
--
You are receiving this mail because:
You are watching all bug changes.
