I have around 80 torrents in my ktorrent view, that i always use (grouped). If i start up ktorrent (paused) and then choose all torrents (at once or in some bulks, same result) to continue, it crashes after a few moments. the kde crash handler coolects data that it ranks useless. if a leave a few unstarted, ktorrent will run smoothly for ages. please give me a hint how to gather more information useful for bug hunting. Reproducible: Always Steps to Reproduce: 1. open ktorrent 2. check "pause torrents" in kde tray and put torrents in pause state 3. restart ktorrent 4. start torrents altogether or in groups 5. see crash after a short while Actual Results: crash Expected Results: no crash
Please add the backtrace of the crash. For more information, please see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Created attachment 85029 [details] backtrace of kcrashhandler
Created attachment 85030 [details] valgrind backtrace
Thanks, could be a Qt or QtWebKit problem. Can you check if disabling the "search" and "syndication" web views helps to resolve the issue?
syndication (never noticed before) was turned off, search was on. after disabling search and restarting, same crash occured again.
seem this bug is invalid since i cant reproduce it anymore. most likely i didnt restart kde after updating and thus resulted into ghostdriven behavior. i'll watch this and request further action if i can reproduce this in a clean environment. sorry for confusion
(In reply to comment #6) > seem this bug is invalid since i cant reproduce it anymore. > most likely i didnt restart kde after updating and thus resulted into > ghostdriven behavior. > i'll watch this and request further action if i can reproduce this in a > clean environment. > sorry for confusion reproduced in clean environment, newly booted and fully up to date. same backtrace as before.
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!