gvfsd-http leaves a lot of sockets in CLOSE_WAIT state

Bug #571970 reported by szu
64
This bug affects 14 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: gvfs-backends

netstat -tp reveals lots of the old connections made by gvfsd-http, and some of them are several days old. this seams like a resource leak. not very harmful for typical user, but the intense use of gvfsd could even block the user from making any new internet connections until the daemon is restarted.

steps to reproduce:

1. use drag&drop to copy a picture from a web browser to the gnome desktop (this uses gvfs internally).
interestingly, copying a content from clickable link did not leave a stale socket (i don't know if this is a rule. "open image in a new tab" and dragging from there was the most reliable way to reproduce the bug)

2. invoke netstat -tp in the console
the socket opened by gvfsd-http wont go away

workaround:
kill the daemon (using killall gvfsd-http) or log out

ProblemType: Bug
Architecture: i386
Date: Fri Apr 30 02:22:47 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gvfs/gvfsd-http
NonfreeKernelModules: nvidia
Package: gvfs-backends 1.4.1-0ubuntu1
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: gvfs
Uname: Linux 2.6.31-20-generic i686

Revision history for this message
szu (szulat) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in gvfs (Ubuntu):
importance: Undecided → Low
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GVFS is available on Maverick and we are wondering if this bug is still an issue for you with that version? Could you please test and comment back? Thanks in advance.

Changed in gvfs (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gvfs (Ubuntu) because there has been no activity for 60 days.]

Changed in gvfs (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Jeffery Wilkins (djcanadianjeff) wrote :

bump for re open this bug is still present in ubuntu trusty

Revision history for this message
poiuty (poiuty) wrote :

confirm (14.04)

# netstat -tupan | grep gvfsd-http
tcp 70 0 192.168.0.100:35449 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:33953 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:49011 91.189.92.10:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:35455 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:41941 162.213.33.165:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:35453 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:44058 91.189.92.11:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:33962 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:44061 91.189.92.11:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:49302 91.189.92.10:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:35454 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:35446 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:35447 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:33661 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:49616 91.189.92.10:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:44357 91.189.92.11:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:35445 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:49604 91.189.92.10:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:35448 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:50801 91.189.92.10:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:33950 91.189.92.7:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:44358 91.189.92.11:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:49305 91.189.92.10:443 CLOSE_WAIT 2338/gvfsd-http
tcp 70 0 192.168.0.100:44362 91.189.92.11:443 CLOSE_WAIT 2338/gvfsd-http

Revision history for this message
drm200 (drm200) wrote :
Download full text (13.1 KiB)

Trusty 14.04 ... still a problem ....... but 760344 implies this is fixed but is not

tcp 1 0 192.168.69.80:47642 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48689 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47602 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47669 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47655 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48748 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48724 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47535 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47570 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47601 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48607 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48753 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48749 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48705 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48669 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47639 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47537 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48643 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48620 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48613 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48734 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47635 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48709 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47540 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48735 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:48691 162.213.33.242:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47679 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd-http off (0.00/0/0)
tcp 1 0 192.168.69.80:47577 162.213.33.241:80 CLOSE_WAIT 3824/gvfsd...

summary: - gvfsd-http leaves a lot of sockets in CLOSE_WAIT state
+ buy adderall online overnight delivery in usa
description: updated
Colin Watson (cjwatson)
summary: - buy adderall online overnight delivery in usa
+ gvfsd-http leaves a lot of sockets in CLOSE_WAIT state
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.