Version: unspecified (using KDE 4.4.4) OS: Linux When using ktorrent's search feature to find a torrent in kickasstorrents.com memory use keeps increasing, filling the whole swap and making the system unusable after a few hours (+4GB memory used). When ktorrent is restarted the problem WILL persist, as the previous loaded site is loaded once more in the background, even if the "search" pane isn't selected. Took me a while to find out that the reason was the search pane, therefore this is reproducible. only happens when i use kickasstorrents.com. Reproducible: Didn't try Steps to Reproduce: 1. open ktorrent; 2. go to "Search", use torrentz.com search engine, and download a torrent from kickasstorrents.com; 3. leave it downloading. Actual Results: Used memory increases, fills in the RAM, and SWAP, eventually it will be necessary to use CTRL + ALT + Backspace to kill Xorg; If left overnight the ktorrent process will have crashed by the morning (i guess it also depends on the amount of ram installed). Expected Results: i'd expect ktorrent to: (a) - Unload the contents of Search pane after it is used. (b) - have some kind of protection for memory leaks caused by the websites viewed. (probably this is more a task for the khtml or konqueror browser devs) WORKAROUND: for the moment i search the torrent i want, start its download, then i return to the search pane and click on "home" to return to the base search webpage.
Ktorrent version is 3.3.4r2
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 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!