After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 651863 - gvfsd-http leaks file handles
gvfsd-http leaks file handles
Status: RESOLVED DUPLICATE of bug 639777
Product: gvfs
Classification: Core
Component: http backend
1.8.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-06-04 18:12 UTC by Jed Brown
Modified: 2012-12-06 10:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jed Brown 2011-06-04 18:12:44 UTC 
Original symptom:
Rhythmbox podcast feeds could not be updated because it was "unable to parse feed contents".

Investigating further:

$ gvfs-info valid-feed-url

fails due to

Error getting info: Error while getting peer-to-peer dbus connection: Failed to create new socket: Failed to open socket: Too many open files

lsof shows that gvfsd-http has 3192 open files. After killing gvfs (and restarting rhythmbox), everything works again.

Additional info:
gvfs-1.8.2-1
rhythmbox-2.90.1.git20110528-1
Arch Linux, kernel 2.6.38

Originally reported: https://bugs.archlinux.org/task/24539
Comment 1 Jan Alexander Steffens (heftig) 2011-07-23 01:52:32 UTC 
Seems gvfsd-http never closes its connections. netstat gets filled with sockets in CLOSE_WAIT state.
Comment 2 Jan Alexander Steffens (heftig) 2011-10-03 19:57:00 UTC 
Still an issue using 1.10.0.
Comment 3 Jan Alexander Steffens (heftig) 2012-04-28 17:00:01 UTC 
Still an issue using 1.12.2.
Comment 4 Jan Alexander Steffens (heftig) 2012-06-16 17:28:57 UTC 
Still an issue using 1.12.3.
Comment 5 Jared González 2012-10-30 16:55:32 UTC 
Still an issue using 1.14.0.
Comment 6 Tomas Bzatek 2012-12-06 10:13:21 UTC 
There are several similar bugs open, let's deal with them together in bug 639777.

*** This bug has been marked as a duplicate of bug 639777 ***