Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.2.0
-
None
Description
see: https://codereview.qt-project.org/#change,67626 & tst_QCoreApplication::testDeferredDeleteFromAboutToBlock
deletion doesn't work until the application exits, leading to massive memory leaks in e.g. QtWayland and xcb which both tie into the dispatcher's signals. probably third party code, too.
Attachments
Issue Links
- is duplicated by
-
QTBUG-49238 OS X: deleteLater() not deleting object before application quit
- Closed
- resulted in
-
QTBUG-120124 Improvements to deferred deletions / deleteLater()
- Open
For Gerrit Dashboard: QTBUG-36434 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
67626,3 | Increment loopLevel prior to emitting aboutToBlock()/awake() signals | stable | qt/qtbase | Status: ABANDONED | -1 | 0 |
142309,24 | Fix for deferredDelete() bug when calling the glib loop directly | dev | qt/qtbase | Status: MERGED | -2 | 0 |
149561,1 | Fix for deferredDelete() bug when calling the glib loop directly | 5.7 | qt/qtbase | Status: ABANDONED | 0 | 0 |
150527,3 | Fix warnings about constructor initialization order in tst_QObject. | 5.7 | qt/qtbase | Status: MERGED | +2 | 0 |