https://bugs.kde.org/show_bug.cgi?id=383655
Emmanuel Lepage Vallée <elv1...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Emmanuel Lepage Vallée <elv1...@gmail.com> ---
Fixed in LRC commits:
f975033
90451b2
6c15860
d07e479
c0248f5
34a11bd
b049fa4
b68614b
5b654eb
93069ba
27e80f3
9f54972
20a8d84
919a265
51c21ad
b9d3bcb
80a0c7f
521b4bc
d1d6634
4f218ef
13d9703
6f66fad
1822fa0
d72d617
5efe711
and Ring-KDE commits:
fb1d7dbd
4d5ec519
3a4d490c
6794cb12
c195481b
Work done:
* Clean all false positive Valgrind issues using a suppression file
* Fix all minor errors detected
* Use Valgrind to redesign the destructor order
* Fix all memory leaks
* Use a GDB script to map the static initialization and destruction order
* Rework the static initialization to ban all QObject from being created
before main()
* Mitigate https://bugreports.qt.io/browse/QTBUG-52988 by moving back the
QApplication into main
* Mitigate https://bugreports.qt.io/browse/QTBUG-40745 by manually deleting
some tree object before QObject::deleteAllChildren
* Mitigate https://bugreports.qt.io/browse/QTBUG-43080 by being more careful
to free the QML engine early
* Implement the QWidget closeEvent for the timelinewindow to make sure the
application quits sanely when using either the QAction or X11 events.
--
You are receiving this mail because:
You are watching all bug changes.
