Description of problem: When sending large files with KDE Connect, system memory usage increases without a similar decrease once the transfer is complete. After transferring ~80 GiB of files from my laptop to my desktop, my laptop's memory usage was at 14.1 GiB of 15.5 GiB available, with about 13.5 GiB of that being kdeconnectd. Performance slowed to a crawl until I killed the kdeconnectd process. There was no such effect on the receiving desktop. I tried sending a single 40 GiB file from my desktop to my laptop and it took up 29 GiB of memory during the transfer, then dropped to 13 GiB afterward. Version-Release number of selected component (if applicable): 1.3.5-1.fc31 How reproducible: Tried once with 80 GiB of files and once with a single 40 GiB file and this happened both times. Steps to Reproduce: 1. Pair two computers via KDE Connect 2. Open Dolphin, right click on a large file, and select "Send to '$foo' via KDE Connect" 3. Open ksysguard and watch the memory usage climb Actual results: Memory usage increases dramatically and doesn't decrease once the transfer is complete. Expected results: Memory should be freed once the transfer is complete. Additional info: Watching this happen in ksysguard, it looks like there are periodic breaks in the file upload. During those breaks, memory usage climbs, at least during the first half of the transfer. It looks like the file is being put into an upload buffer, but the buffer isn't completely cleared once the transfer is complete.
Ideally, this would be best reported upstream @ bugs.kde.org There's likely little that we can do ourselves to address this without their collaboration.
Alright, I've reported this upstream. The report may be found at https://bugs.kde.org/show_bug.cgi?id=414538.
thank you
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.