diff options
| author | Giuseppe D'Angelo <giuseppe.dangelo@kdab.com> | 2014-09-20 18:52:15 +0200 |
|---|---|---|
| committer | Giuseppe D'Angelo <giuseppe.dangelo@kdab.com> | 2014-09-22 18:56:50 +0200 |
| commit | 8c2f0ac3827e765dfd31711ad576b396df7df467 (patch) | |
| tree | 41d83582251181149f8e9df64d03c0003979e3e3 /src/gui | |
| parent | d9e1a0f05b30fd646a6b473bea605f6054bf0e67 (diff) | |
QObject: fix a memory leak in moveToThread
For some reason it seems to be supported to call moveToThread(0).
That call will allocate a new QThreadData for the object. However,
if we then detect that we're calling moveToThread from a thread
which is not the one the QObject has affinity with,
we error out leaking that QThreadData object.
Change-Id: I0fe6625a2a9887535e457f3897b514d2a03d1480
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Marc Mutz <marc.mutz@kdab.com>
Diffstat (limited to 'src/gui')
0 files changed, 0 insertions, 0 deletions