Bug 292109

Summary:	[4.7.97] kio_ftp runaway process caused by stalled kget download
Product:	[Unmaintained] kio	Reporter:	Andreas Sturmlechner <asturm>
Component:	ftp	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	adawit
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.9-Git
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Dr.Konqi crash report on segfaulted kget when clicked as tray icon

Description Andreas Sturmlechner 2012-01-21 13:19:09 UTC

Version:           Git (using Devel) 
OS:                Linux

My system was plagued by a kio_ftp process re-appearing every few minutes and causing 100% CPU load. After lots of wondering, finally I found the reason to be a leftover download in the kget widget that was stalled at 99%.

Reproducible: Didn't try

Steps to Reproduce:
I'm not sure how to reproduce this as how to find another (ftp-)download to stall at some point... I removed the item that was plaguing my notebook fan from kget to solve the issue.

Anyway, to (try to) reproduce:
1. download something from an ftp server
2. after reboot, find the download to be stalled at some point
3. watch kio_ftp go nuts in `top`
4. kill the kio_ftp process
5. watch it go nuts all over again after some minutes


Expected Results:  
Download stalled or not, this isn't supposed to happen.

I'll happily provide any additional information that might be of use.

Comment 1 Leszek Lesner 2012-07-01 10:29:18 UTC

Created attachment 72256 [details]
Dr.Konqi crash report on segfaulted kget when clicked as tray icon

Comment 2 Dawit Alemayehu 2012-09-29 06:55:05 UTC

Are you sure this is not a kget bug ? I do not use kget and I have never ever seen such a bug ; so the question to you is can you replicate the problem if you disable kget and simply do the download directly ?

Comment 3 Andrew Crouthamel 2018-09-23 02:19:04 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 set the bug status 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 4 Andrew Crouthamel 2018-10-27 04:14:36 UTC

Dear Bug Submitter,

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!