Package: gvfs
Version: 0.2.5-1
Severity: serious
Reasoning: cripples things that might wait for it

Hi,

when running the attached program with ~/.gvfs/localtest/mirror/debian (or 
whereever you
have a sizable collection of files) for a while, gvfsd becomes unresponsive and 
apparently
does not answer dbus requests for that gvfs-mount anymore. This happens with 
multiple
backends (e.g. sftp and localtest). Other mounts appear to be still working.
This does not seem to be a mere gvfs-fuse-daemon-problem because gvfs-ls is 
affected as
well. I noticed this problom while testing a patch for the gvfs-fuse RC bug. 
Error message is

$ gvfs-ls localtest:/home
Error: Error while getting peer-to-peer dbus connection: 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.

Kind regards

T.
-- 
Thomas Viehmann, http://thomas.viehmann.net/
#!/usr/bin/python

import os, sys, glob, random, thread
BLOCK = 1024*1024
def madseek(rootdir):
  while 1:
    p = rootdir
    while os.path.isdir(p):
        d = glob.glob(os.path.join(p, '*'))
        if not d:
            break
        p = d[random.randint(0,len(d)-1)]
    if os.path.isfile(p):
        print p
        size = os.stat(p).st_size
        f = open(p)
        pos = random.randint(0,max(size-BLOCK,0))
        f.seek(pos)
        f.read(min(BLOCK,size-pos))
        f.close()

a = map(lambda x: thread.start_new_thread(madseek, (sys.argv[1],)), range(10))
madseek(sys.argv[1])

Reply via email to