GNOME Bugzilla – Bug 549463
Nautilus hangs and consumes huge amounts of memory when browsing smb shares
Last modified: 2018-09-21 16:25:16 UTC
Please describe the problem: When I use Nautilus to browse a server with 2000+ directories, Nautilus hangs and sometimes begins to slowly consume large amounts of memory. Sometimes Nautilus will return and report "0 items" (when browsing the top level of the share) or sometimes reports the following when directly including a subdirectory in the URI Error: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Please select another viewer and try again. Since I have experienced this bug for a couple of years now I believe the problem is not with the vfs backend since Nautilus has used both gnome-vfs and gvfs implementations. Steps to reproduce: 1. Setup a Windows server/share with 2000+ subdirectories 2. Specify just the share. This should return "0 items" 3. Specify the share + sub-direcotry. This should return with the dbus error. 4. If the backend is gnome-vfs I believe Nautilus will consume massive amounts of memory before OOM kicks in. Actual results: Expected results: Browse the share. Does this happen every time? Yes. Other information:
-> gvfs/smb Moving to gvfs.
I have a similar bug on Ubuntu/LP: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/259771
Cosimo Cecchi, I am not sure why you moved this bug to gvfs. Notice that in the problem description I have been following "this bug for a couple of years now" and the problem exists whether gnome-vfs or gvfs is the backend. The reasonable conclusion is that the problem is NOT gvfs. Bryan
Bryan, I moved the bug to gvfs because I/O operations for SMB shares are completely managed by gvfs, there's nothing that we can do in Nautilus. The fact that the bug was there in gnome-vfs doesn't mean that the same bug couldn't be in gvfs as well, as I suppose both the gnome-vfs and gvfs SMB modules share some common code. For example, try to create 2500 subdirectories in a local path and open the path with Nautilus; you won't be able to trigger the bug, which means that this is specific to SMB.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/57.