Bug 366488

Summary:	Too many sftp.so processes, not closing
Product:	[Frameworks and Libraries] kio-extras	Reporter:	Nikita Skovoroda <chalkerx>
Component:	SFTP	Assignee:	Plasma Development Mailing List <plasma-devel>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	nate, ritalat, sitter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Nikita Skovoroda 2016-08-07 07:24:02 UTC

It looks like something constantly spawns new sftp.so processes without killing the old ones.

Atm, I have 110 running sftp.so processes totalling to over 1 GiB RSS. I'm sure I don't have that many sftp directories open.

Reproducible: Always

Steps to Reproduce:
0. Kill all Dolphin and sftp.so instances (or just make sure those are not running) 
1. Open Dolphin
2. Open something over sftp:// protocol.
3. Wait about a minute.
4. Navigate to another, local directory
5. Open something else over sftp:// protocol in the same tab
6. Wait about a minute.
7. Open a new tab poiting to a local directory and close the first tab


Actual Results:  
1. There are 0 sftp.so processes running, totalling in 0 MiB.
2. There are 4 sftp.so processes running, totalling in 16 MiB.
3. There are 5 sftp.so processes running, totalling in 20 MiB.
4. There are 5 sftp.so processes running, totalling in 20 MiB.
5. There are 8 sftp.so processes running, totalling in 32 MiB.
6. There are 10 sftp.so processes running, totalling in 40 MiB.
7. There are 10 sftp.so processes running, totalling in 40 MiB.

Expected Results:  
I expect sftp.so old processes to be killed after a certain amount of time if they couldn't be reused.

Some of the sftp.so processes present are over a month old.

Comment 1 Harald Sitter 2020-03-04 14:05:46 UTC

Is this still a problem? Does this happen when talking to more than one or two servers?

There should be guards in place to limit the amount of concurrent processes in general and specifically per host as well, so it sounds a bit like the processes may have gotten stuck on shutdown. As in: KIO doesn't know about them anymore but they are still there.

Comment 2 Harald Sitter 2020-03-04 14:05:58 UTC

status

Comment 3 Bug Janitor Service 2020-03-19 04:33:13 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 4 Bug Janitor Service 2020-04-03 04:33:14 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!