Ubuntu
duplicity package

duplicity stalls the system grabbing whole available memory and swapping (3GB+) (REGRESSION)

Bug #936291 reported by Paul Ortyl on 2012-02-19

This bug report is a duplicate of: Bug #971665: Full system backup hangs at 100% and makes the whole system very unresponsive - BackendException: Got status code 400. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	duplicity (Ubuntu)	New	Undecided	Unassigned

Bug Description

Duplicity grabs all available memory, gets into swap and renders system unusable.
I have killed the process at is have taken more than 3GB of RAM.
There was no problem with the same setup under 11.10, so this is definitely regression.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: duplicity 0.6.17-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Sun Feb 19 16:32:28 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120213)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Paul Ortyl (ortylp) wrote on 2012-02-19:

Dependencies.txt Edit (907 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (137 bytes, text/plain; charset="utf-8")

Revision history for this message

Paul Ortyl (ortylp) wrote on 2012-02-25:

seems to be related/duplicate of to #908228,

Revision history for this message

Paul Ortyl (ortylp) wrote on 2012-02-25:

https://bugs.launchpad.net/duplicity/+bug/908228

Revision history for this message

papukaija (papukaija) wrote on 2012-09-30:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 971665, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.