Fix a memory leak in TransferJob
TransferJob wasn't releasing its QNetworkReply upon deletion, which resulted in it and associated resources being leaked. With the many requests spotted in bug 485799 this leads to heavy resource usage.
| Heaptrack Before | Heaptrack After |
|---|---|
 |
 |
Edited by Louis Moureaux