Please help: Download file from server using HTTP/2 protocol consumes too much RAM
-
This post is deleted!
-
Hi and welcome to devnet,
Since QNetworkReply is a QIODevice, why not use readyRead and read the data as they arrive ?
-
Hi and welcome to devnet,
Since QNetworkReply is a QIODevice, why not use readyRead and read the data as they arrive ?
-
My bad, the code rendering is sometime tricky.
Even if locked with 5.9.6, can you check if it works better with a more recent version of Qt ?
-
My bad, the code rendering is sometime tricky.
Even if locked with 5.9.6, can you check if it works better with a more recent version of Qt ?
wrote on 6 Jun 2021, 07:16 last edited bySince all my projects are using Qt 5.9.6 so I cannot upgrade to newer version now (it will take time to make everything works fine with recent Qt version).
I wonder if we have a solution for this (or root cause is ok) -
The fact that you are locked to 5.9.6 is well understood, my suggestion is to check whether it's still the case with a more recent version of Qt and if it's the case, you might be able to backport said fix. You do not need to re-build your whole application, just make a minimal app that does the download to observe the effect.
-
wrote on 6 Jun 2021, 23:46 last edited by
Got it, let me try.
Thanks a lot for your help. -
wrote on 7 Jun 2021, 04:55 last edited byThis post is deleted!
-
It still would be nice if you can try to reproduce it with 5.15.x and if it still happens without you start/endTransaction() stuff, create a bug report so it gets fixed. I don't have a http/2 server for testing here so can't try it out by myself.
-
wrote on 7 Jun 2021, 07:05 last edited by
Sorry I forgot to enable HTTP/2. I re-checked again and RAM is still increased.
You can test by downloading file from here:
https://download-installer.cdn.mozilla.net/pub/firefox/releases/89.0/linux-x86_64/en-US/firefox-89.0.tar.bz2
This server is using HTTP/2 protocol. -
wrote on 13 Jul 2021, 03:53 last edited by Thuong Le
I've tried with 5.12 and the problem is not happening. Maybe it is a bug of 5.9.6