Bug 330855

Summary: Starting all torrents in one view results in segfault crash. Subsets of torrents still work
Product: [Applications] ktorrent Reporter: Georg Schlisio <g.schlisio>
Component: generalAssignee: Joris Guisson <joris.guisson>
Status: RESOLVED WORKSFORME    
Severity: crash CC: cfeck, g.schlisio
Priority: NOR    
Version First Reported In: 4.3.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: backtrace of kcrashhandler
valgrind backtrace

Description Georg Schlisio 2014-02-06 15:19:38 UTC
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
Comment 1 Christoph Feck 2014-02-06 20:32:36 UTC
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
Comment 2 Georg Schlisio 2014-02-07 09:01:23 UTC
Created attachment 85029 [details]
backtrace of kcrashhandler
Comment 3 Georg Schlisio 2014-02-07 09:02:08 UTC
Created attachment 85030 [details]
valgrind backtrace
Comment 4 Christoph Feck 2014-02-07 09:33:21 UTC
Thanks, could be a Qt or QtWebKit problem. Can you check if disabling the "search" and "syndication" web views helps to resolve the issue?
Comment 5 Georg Schlisio 2014-02-07 09:37:17 UTC
syndication (never noticed before) was turned off, search was on.
after disabling search and restarting, same crash occured again.
Comment 6 Georg Schlisio 2014-02-14 11:44:01 UTC
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
Comment 7 Georg Schlisio 2014-02-20 09:16:52 UTC
(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.
Comment 8 Andrew Crouthamel 2018-10-31 03:56:33 UTC
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!
Comment 9 Bug Janitor Service 2018-11-15 10:44:46 UTC
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!
Comment 10 Bug Janitor Service 2018-11-30 03:57:05 UTC
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!