Question

在我有QOBJects的申请中,所有申请都包含QNetworkAccessManager。我知道,我只建议每次申请一次,但既然我再说6次,我需要这样做。因此,这就是我如何开始直线。

FileUploader *fileUploader = new FileUploader(_fileList);
QThread *fileUploaderThread = new QThread();
fileUploader->moveToThread(fileUploaderThread);

// uploader > model
connect(fileUploader, SIGNAL(progressChangedAt(int)), _model, SLOT(reportProgressChanged(int)), Qt::QueuedConnection);
connect(fileUploader, SIGNAL(statusChangedAt(int)), _model, SLOT(reportStatusChanged(int)), Qt::QueuedConnection);
// uploader > its thread
connect(fileUploader, SIGNAL(canceled()), fileUploaderThread, SLOT(quit()), Qt::QueuedConnection);
connect(fileUploader, SIGNAL(finished()), fileUploaderThread, SLOT(quit()), Qt::QueuedConnection);
// uploader > this
connect(fileUploader, SIGNAL(canceled()), this, SLOT(deleteFinishedUploader()), Qt::QueuedConnection);
connect(fileUploader, SIGNAL(finished()), this, SLOT(deleteFinishedUploader()), Qt::QueuedConnection);
connect(fileUploader, SIGNAL(finishedCurrentUpload()), this, SLOT(uploadNextFileOrFinish()), Qt::QueuedConnection);
// thread > this
connect(fileUploaderThread, SIGNAL(finished()), this, SLOT(checkIfAllThreadsAreFinished()), Qt::QueuedConnection);
connect(fileUploaderThread, SIGNAL(finished()), this, SLOT(deleteFinishedThread()), Qt::QueuedConnection);
// this > uploader
connect(this, SIGNAL(cancel()), fileUploader, SLOT(cancel()), Qt::QueuedConnection);

fileUploaderThread->start();
QMetaObject::invokeMethod(fileUploader, "init", Qt::QueuedConnection);
QMetaObject::invokeMethod(fileUploader, "uploadAt", Qt::QueuedConnection, Q_ARG(int, startIndex));

QMutexLocker locker(&_mutex);
_threadCount++;

每一条都从一个清单的索引开始,以便它们能够清点它们需要上载和着手处理大约5个步骤(与QNetworkAccessManager的电话)。如无其他设备上载,文档上载器信号“成()”,即<代码>deleteFinishedThread和<编码>。在我这样做的地方:

QThread *thread = qobject_cast<QThread*>(sender());

if(thread != NULL) thread->deleteLater();

或

FileUploader *fileUploader = qobject_cast<FileUploader*>(sender());

if(fileUploader != NULL) fileUploader->deleteLater();

它们在做完时可以删除read子。

The issue is that every time I start (f或example) 3 threads that have 1 file to upload and handle each, the thread count gets increased by 8-10. This means that the thread count goes from about 5 to 100 if I restart the uploading process a few times.

我做了什么错误? 或者,我使用“Windows Task Manager”来控制这一问题的最大问题吗? 我把我删除的QNAM的所有答复都交给我,所有答复似乎都已删除,但我仍然对我的头部表示赞扬,因为笔迹不断上升。

EDIT: In my fileuploader I create an object(Manager) on the heap which has a QNetworkAccessManager on the stack. When the fileuploader gets deleted it calls "deleteLater()" on the Manager but it never gets deleted. We tried to delete the Manager and set it to NULL but that gave us an access violation since the Manager wasn t done yet (the QNetwork.dll reported the issue so it must be something inside the QNAM that is running still). The times when we didnt get access violation, the object was deleted and the thread count went back to normal. What can live inside the QNAM and prevent me from deleting it when it goes out of scope? Should I create the QNAM on the heap instead? At this stage non of the destructors are being called even when calling deleteLater()...

此外,我如何减少处理点?

Answer 1

在很多“几乎放弃”之后,我就找到了read子的解决办法。确实,Synxis对位置顺序所说的话。

然而,我仍然与档案库有一些问题,如果有人能够更好地回答我很高兴接受这一点的话。

我的法典改为:

...
// uploader > this
connect(fileUploader, SIGNAL(canceled()), this, SLOT(deleteFinishedUploader()), Qt::QueuedConnection);
connect(fileUploader, SIGNAL(finished()), this, SLOT(deleteFinishedUploader()), Qt::QueuedConnection);
// uploader > its thread
connect(fileUploader, SIGNAL(destroyed()), fileUploaderThread, SLOT(quit()));

这意味着,当目标被删除时,已经停止(放弃)。尽管文件指出:

这一信号在物体被销毁之前即刻发出,不能阻挡。

在发出这一信号之后,所有物体立即销毁。

哪一种意思是,这种信号仅仅被放弃,任何东西都会被销毁(这意味着我将在上载者被删除之前放弃对面)? 不够好,可能更好。 HOWEVER, atm, my'thread amount go out a bit each time the uploaders endes and re to norm after a 20sec or so (a several “watcher-threads” must be die by各窗户等)。

Answer 2

我可能错了,但我认为你发出信号存在问题:

// uploader > its thread
connect(fileUploader, SIGNAL(canceled()), fileUploaderThread, SLOT(quit()), Qt::QueuedConnection);
connect(fileUploader, SIGNAL(finished()), fileUploaderThread, SLOT(quit()), Qt::QueuedConnection);
// uploader > this
connect(fileUploader, SIGNAL(canceled()), this, SLOT(deleteFinishedUploader()), Qt::QueuedConnection);
connect(fileUploader, SIGNAL(finished()), this, SLOT(deleteFinishedUploader()), Qt::QueuedConnection);

Remember that when multiple slots are connected to the same signal, they re executed in the order of connection. Here, when the fileUploader will be finished, it will call finished() which will first call the quit() method of the thread, and then the deleteFinishedUploader() method. Same for the canceled() signal. But, meanwhile, the thread was finished, so no event processing for the fileUploader can be done (consequence of the moveToThread(...)). deleteLater() needs event processing, thus your fileUploader will never be deleted...

安排您的联系方式不会达到100%:delete Later(<><>/code>,可在无事件处理的情况下立即撤离。



解决办法可以是将“move ToThread()上载到主线上,或放在仍在处理其事件的透镜上。

Answer 3

不是答案,而是:

    fileUploaderThread->start();
    QMetaObject::invokeMethod(fileUploader, "init", Qt::QueuedConnection);
    QMetaObject::invokeMethod(fileUploader, "uploadAt", Qt::QueuedConnection, Q_ARG(int, startIndex));

也就是说,你开始哪怕是空档,然后,你提出要执行的空档或信号。 Assume (in general) that there are other QObject in this read. 由于活动场所已经启动,有可能将这些场所或信号付诸实施。如果你希望“init”和“uploadAt”成为事件发生时首先要采用的方法,那么你在开始活动之前就请他们发言。 (如果read不开始,就永远不会执行)。

http://qt-project.org/doc/qt-4.8/qmetaobject.html#invokeMethod” rel=“nofollow”>QMetaObject:invokeMethod:

If type is Qt::QueuedConnection, a QEvent will be sent and the member is invoked as soon as the application enters the main event loop.

在此情况下,这项活动被送至现场活动。

友情链接