Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P2: Important
Fix Version/s: 6.8.1, 6.9.0 FF
Affects Version/s: 6.8.0
Component/s: Core: Threads
Labels:
None

Platform/s:

Windows
Commits:
c57027199 (dev), d6c592aa2 (6.8), 4678d96d8 (dev), 1487d7edb (6.8)

I observe a behavior change in 6.8.0: Despite setting setExpiryTimeout(-1) on QThreadPool, QThread::currentThreadId() returns more different IDs than maxThreadCount() would allow. Short program for testing:

#include <QCoreApplication>
#include <QThreadPool>
#include "qmutex.h"
#include "qtimer.h"

int main(int argc, char *argv[])
{
    QCoreApplication a(argc, argv);

    QThreadPool::globalInstance()->setExpiryTimeout(-1);
    QSet<int64_t> threadids;
    QMutex mutex;
    QTimer t;
    QObject::connect(&t,&QTimer::timeout,&t,[&threadids, &mutex]() {
        for(int i=0;i<10000;++i) {
            QThreadPool::globalInstance()->start([&threadids, &mutex]() {
                QMutexLocker locker(&mutex);
                threadids.insert(reinterpret_cast<int64_t>(QThread::currentThreadId()));
                qDebug()<<threadids.size();
            });
        }
    });
    t.start(1000);


    return   a.exec();
}