How to use QNetworkAccessManager without leaking memory.

Christian Ehrlicher

@Q139 This example contains a custom local eventloop. And this loop is not stopped due to while(1) around it. This is plain wrong.
Then you create a new request every millisecond and don't delete it.

Q139

@Christian-Ehrlicher How to delete request?

void Form::httpFinished()
{
    reply->deleteLater();
    finished=1;
 //  reply=NULL;
}

It should catch this function via event loop every time before new request, here it sets reply for deletion.

Christian Ehrlicher

@Q139 Ah, the strang finished=1 does it.
Again: don't block, use async signals/slots.

Your deleteLater() is the problem since you never return to the event loop. See the documentation: "The object will be deleted when control returns to the event loop. "
Creating a new eventloop will not help - it's a new one, not the one where the object was created in.

Q139

@Christian-Ehrlicher Does QApplication::processEvents(); not go trough deleteLater()'s event loop?

while(!finished){
    QThread::msleep(1);
    QApplication::processEvents();<--
}

At least it fires signals&slots events.

Christian Ehrlicher

@Q139 said in How to use QNetworkAccessManager without leaking memory.:

At least it fires signals&slots events.

It executes the event loop, it does not return to it. It would be dangerous to delete objects during processEvents() since you can still be in a slot which object was deferred for deletion.

Again: you don't need it and it's dangerous to call processEvents() or spin a local event loop. Avoid it as much as possible.

Q139

@Christian-Ehrlicher Then its solved, i tryed to bodge together networking by not returning from the while loop.
Assumption was that QApplication.processEvents() runs all functions of event loop including deletions.
It was for temprorary app i bodged together to collect data via certain api, but there is alot to get and many requests eat memory up.
Even bodging stuff together requires correct knowledge of how underliying functions works...

Is there a way to force deletion events from the while(1) event loop?

void Form::httpFinished()
{
    disconnect(reply, &QNetworkReply::finished, this, &Form::httpFinished);
    delete reply;
    finished=1;
 //  reply=NULL;
}

using delete reply; still grows memory

Q139

Without while loop i still notice memory usage growth , what am i missing here?
However it jumps back in memory usage after some periods, but still goes 100+mb eventualy.

#include "form.h"
#include "ui_form.h"
#include <QtNetwork>
#include <QUrl>
#include "QProgressDialog"
#include "QMessageBox"
#include "QTextBlock"
#include "qcoreapplication.h"
Form::Form(QWidget *parent) :
    QWidget(parent),
    ui(new Ui::Form)
{
    ui->setupUi(this);

    connect(this,SIGNAL(nextReq()),this,SLOT(startRequest()));//<--- to loop


#ifndef QT_NO_SSL
    connect(&qnam, &QNetworkAccessManager::sslErrors,
            this, &Form::sslErrors);
#endif

}

Form::~Form()
{
    delete ui;
}


bool finished=0;
void Form::on_pushButton_clicked()
{

ui->pushButton->hide();


    QUrl ur("test");
    startRequest();


}

bool once=1;
void Form::startRequest()
{
    QThread::msleep(1);
    qnam.clearAccessCache();
    qnam.clearConnectionCache();
    
    reply = qnam.get(QNetworkRequest(url));
    connect(reply, &QNetworkReply::finished, this, &Form::httpFinished);

}

void Form::httpFinished()
{
    disconnect(reply, &QNetworkReply::finished, this, &Form::httpFinished);
    reply->deleteLater();

    emit nextReq();
 //  reply=NULL;
}

JonB

@Q139
Not knowing much about electricity, your picture above is how I power my PCs. Is there anything wrong with this setup?

Q139

@JonB
For temporary solution i think its great way to power computer/s if you really needed the power and had no access to better options.

One possible bad scenario is ,if you add more PCs and increase load at some point it may act as fuse, after breaking connection short circuit and consequently breaking main fuse of the house if reasonable short circuit occurs, or just catching fire.

Maybe something corrodes over the years and starts to heat, then you will get FREE house heater out of it as well in addition to powering pc, works best on wooden house.

Connections using proper wires:

Bonnie

I replace you sleep with timer, does this change anything?

#include "form.h"
#include "ui_form.h"
#include <QtNetwork>
#include <QUrl>
#include "QProgressDialog"
#include "QMessageBox"
#include "QTextBlock"
#include "qcoreapplication.h"
Form::Form(QWidget *parent) :
    QWidget(parent),
    ui(new Ui::Form)
{
    ui->setupUi(this);

#ifndef QT_NO_SSL
    connect(&qnam, &QNetworkAccessManager::sslErrors,
            this, &Form::sslErrors);
#endif

}

Form::~Form()
{
    delete ui;
}

void Form::on_pushButton_clicked()
{
    ui->pushButton->hide();
    startRequest();
}

void Form::startRequest()
{    
    qnam.clearAccessCache();
    reply = qnam.get(QNetworkRequest(url));
    connect(reply, &QNetworkReply::finished, this, &Form::httpFinished);
}

void Form::httpFinished()
{
    reply->deleteLater();
    QTimer::singleShot(1000, this, &Form::startRequest);
}

Q139

@Bonnie Unfortunately not.

QNetworkAccessManager qnam;
QNetworkReply *reply;

void Form::startRequest()
{
    qnam.clearAccessCache();
    reply = qnam.get(QNetworkRequest(QUrl("www.microsoft.com")));
    connect(reply, &QNetworkReply::finished, this, &Form::httpFinished);
}

void Form::httpFinished()
{
     disconnect(reply, &QNetworkReply::finished, this, &Form::httpFinished);
    reply->deleteLater();
    QTimer::singleShot(1, this, &Form::startRequest);
}

This sums the core code up..
If someone plans to use it as ddos code it will probably flood your own memory up instead.

Bonnie

@Q139 Actually, I don't get a increasing memory while testing the last and the previous code of yours.
I wonder if it needs to be tested with a url that have a big size of reply data...
I'm using Qt 5.12 though...

Christian Ehrlicher

@Q139 said in How to use QNetworkAccessManager without leaking memory.:

If someone plans to use it as ddos code it will probably flood your own memory up instead.

No it won't - there is no leak in this code anymore.
The disconnect() is not needed though.

Q139

I still get leak.
alt text

Could you check if application output gives SSL error while connecting to https site?
I also had to install openSSL in addition to get it working, maybe it is related to that.
And while tested on ubuntu got no leak , but it had SSL errors in app output.
Got SSL for win7 and win10 from here, the lite edition, maybe that component causes problems.

Q139

@Bonnie Used invalid url text , like "test" also and got leak.

Q139

Install openSSL on Windows 7 or 10 and see if the app below leaks memory.

Windows ssl libraries site
direct link to download-Win64 OpenSSL v1.1.1g Light

Project file

Q139

Current solution to use QNetworkAcessManager 50 times:
I thought maybe using just once and deleting gives overhead.
This way it goes to ~100mb and back to ~20mb all the time, instead of gb+


int qnamUses=0;
QNetworkAccessManager *qnam=new QNetworkAccessManager;
QNetworkReply *reply;

void Form::startRequest()
{
    qnamUses++;
    if(qnamUses>50){
            qnam->deleteLater();

      qnam=new QNetworkAccessManager;
    }

    reply = qnam->get(QNetworkRequest(QUrl("www.microsoft.com")));
    connect(reply, &QNetworkReply::finished, this, &Form::httpFinished);
}

void Form::httpFinished()
{
  //  qnam.clearAccessCache();
    //qnam->deleteLater();
    reply->deleteLater();
    QTimer::singleShot(0, this, &Form::startRequest);
}

jsulm

@Q139 said in How to use QNetworkAccessManager without leaking memory.:

qnam=new QNetworkAccessManager;

Why do you create QNetworkAccessManager instance for each request? One can handle many requests...

Q139

@jsulm For 50 requests , then schedule for deletion. to prevent memory usage growth.
Maybe i am using something incorrectly.

SGaist

You never reset qnamUses. Therefore after 51 requests, you recreate your qnam object for every request.