Bug 148307

Summary: kio_http processes remaining after firefox closed
Product: [Unmaintained] kio Reporter: lukiki blondo <lblondo>
Component: httpAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: ahartmetz, angel_blue_co2004
Priority: NOR    
Version: 0.2   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description lukiki blondo 2007-07-29 04:28:25 UTC
Version:           0.2 (using KDE KDE 3.5.4)
Installed from:    Mandriva RPMs
OS:                Linux

When I click on a news header, a popup window indicates the link of the page that will be displayed in a browser.

At the same time a kio_http process is created.

After the page has been downloaded, the popup closes and the page is displayed correctly in firefox (which I associated to the htm/html file types in my KDE settings) in a new tab.

When I close firefox, I can still see the related kio_http processes in the process list.

After reading 30 news from the ticker, that makes 30 remaining useless kio_http processes.

I need to kill them manually to avoid PC overload.

I think the kio_http processes should terminate automatically after passing the link to firefox, and they don't, which constitutes the bug.
Comment 1 Angel Blue01 2009-03-04 17:24:16 UTC
I agree, that doesn't sound like it should do that...
Comment 2 Andreas Hartmetz 2009-07-21 19:08:53 UTC
When you click on a news header where? In some plasmoid? Akregator?
Comment 3 Dawit Alemayehu 2011-01-05 00:56:32 UTC
SVN commit 1211792 by adawit:

- Fixed KIO::SchedulerPrivate::heldSlaveFor to correctly reuse ioslaves that are on hold.
  See http://svn.reviewboard.kde.org/r/6271/ for details.

BUG:148307
BUG:123121


 M  +14 -3     scheduler.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1211792
Comment 4 Dawit Alemayehu 2011-04-18 03:20:21 UTC
Git commit 5c65f468d016961e7e0bf877e56d475bc302f552 by Dawit Alemayehu.
Committed on 18/04/2011 at 03:23.
Pushed by adawit into branch 'KDE/4.6'.

Mostly revert the changes I made with commit d27c820581673040e80c46087b34b76e9fc9ed79.

I completely misunderstood the main concept behind put slave on hold. With the exception
of corner-case that can only be solved at the application level, putting slaves on hold
should work correctly once this partial revert is commited.

CCBUG:123121
CCBUG:148307
REVIEW:6271

M  +7    -11   kio/kio/scheduler.cpp     

http://commits.kde.org/kdelibs/5c65f468d016961e7e0bf877e56d475bc302f552