Hello, I'm not sure if this is a KGet issue or the new notification system issue (I'll explain above). Reproducible: Always Steps to Reproduce: 1. Start a couple of downloads with KGet (I've put to download a couple of distro ISOs (files between 800MB to 4GB)) 2. You'll notice a huge lagging in the desktop and this is because the X process has jumped up to 100% cpu 3. If you stop the downloads everything returns back to normal immediately This lagging might be from KGet, but I'm inclined to believe it might be caused by the new notification system where it has to monitor the file transfers (the KGet Transfers) and that might be causing the lagging. I'm putting this bug as Grave because the software is basically unusable now.
Created attachment 77776 [details] snapshot.png Here's a screenshot of the situation.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thanks for the report Denis. I've just tried to replicate the issue on kget 20.08.3 and I don't get any lag or high CPU usage. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!