Bug#676840: duplicity leaks resources while restoring

Package: duplicity
Version: 0.6.18-2
Severity: normal

I've been running daily incremental backups for about 10 months. Recently I
tried to restore a file I accidentally deleted, only to find that duplicity
ran out of space. Some investigation revealed that duplicity leaks several
kinds of resources:

1) gpg processes (not zombies)
2) pipes used to communicate with gpg
3) temporary files
3.1) in the directory specified with --tempdir
3.2) in /tmp (deleted but held open)

The last one is especially problematic for me, since /tmp is on a tmpfs and
I don't want to grow it too large (and there's no telling how much would be
needed; 4GB is not enough).

Shortly before running out of space, duplicity had used 1126 file descriptors,
285 gpg processes and 281 temporary files in the designated tempdir totalling
nearly 23GB. After duplicity had terminated, it took nearly ten minutes for
all the gpg processes to finish their own cleanup and release the resources
(disk space) they were holding.

Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.1-core2 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages duplicity depends on:
ii libc6 2.13-33
ii librsync1 0.9.7-9
ii python 2.7.3~rc2-1
ii python-gnupginterface 0.3.2-9.1
ii python2.7 2.7.3~rc2-2.1

Versions of packages duplicity recommends:
ii python-paramiko <none>
ii rsync 3.0.9-1

Versions of packages duplicity suggests:
pn lftp 4.3.7-1
pn ncftp <none>
pn python-boto <none>
pn python-cloudfiles <none>
pn python-gdata <none>
pn python-pexpect 2.4-1
pn tahoe-lafs <none>




To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org