Bug 1067312

Summary: gvfsd-sftp beging consume 100% CPU when I try connect to already shutdown server.
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alexl, bnocera, oholy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-29 19:56:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
htop screenshot
none
backtraces of gvfsd-sftp
none
htop screenshot none

Description Mikhail 2014-02-20 07:58:21 UTC
Created attachment 865357 [details]
htop screenshot

Description of problem:
gvfsd-sftp beging consume 100% CPU when I try connect to already shutdown server.

Comment 1 Mikhail 2014-02-20 08:08:30 UTC
Created attachment 865371 [details]
backtraces of gvfsd-sftp

Comment 2 Mikhail 2014-02-20 08:08:53 UTC
Created attachment 865372 [details]
htop screenshot

Comment 3 Fedora End Of Life 2015-05-29 10:59:27 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.