Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
4.8.2, 5.0.0 Beta 1
-
731ba8ed08f80644b403556638c7f6229e678ebe
Description
Run tst_qfuture with valgrind to verify this:
$ valgrind --tool=memcheck --leak-check=full ./tst_qfuture
Attached is the output I've got.
Context: Because of this Qt Creator might leak memory while searching (among other things). See QTCREATORBUG-7839.
Attachments
Issue Links
- is required for
-
QTCREATORBUG-7839 Memory leak on searches
-
- Closed
-
- resulted in
-
QTBUG-28242 Leaking memory in QtConcurrent::ResultStore<T>::addResults
-
- Closed
-
For Gerrit Dashboard: QTBUG-27224 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
35961,1 | fix memory leak in QtConcurrent | master | qt/qtbase | Status: ABANDONED | 0 | 0 |
37333,2 | Fix for memory leak in ResultStore | master | qt/qtbase | Status: MERGED | +2 | 0 |
38822,4 | Fix for memory leak in ResultStore | 4.8 | qt/qt | Status: MERGED | +2 | 0 |
38825,5 | QtConcurrent: Fix for leak in QFuture | 4.8 | qt/qt | Status: MERGED | +2 | 0 |
39479,2 | QtConcurrent: Fix for leak in QFuture | 4.8 | qt/qt | Status: ABANDONED | -2 | 0 |