possible memory leak
Bug #908228 reported by
Feanor
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I used deja-dup 21.1 to backup and after running for 3 hours duplicity was using up about 2GB of RAM.
Could this point to a memory leak?
duplicity 0.6.17-3
arch linux
Related branches
lp:~mterry/duplicity/memleak
- duplicity-team: Pending requested
-
Diff: 27 lines (+10/-1)1 file modifiedduplicity/util.py (+10/-1)
Changed in duplicity: | |
importance: | Undecided → Medium |
milestone: | none → 0.6.18 |
status: | New → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm seeing similar behavior. I'm using duplicity directly on Ubuntu Natty i386. 0.6.16 is affected but 0.6.15 is not.
It seems to scale with the number of files. On a sample tree with 100,000 files, if you watch with top, 0.6.15's virtual size stays around 25MB throughout the run, while 0.6.16 continues to grow, finishing over 100MB. With more files the effect is more dramatic; with my regular 450,000 file backup, the machine ran out of memory (it has 2G physical and 3G swap). So this is a serious bug IMHO.
I checked some revisions on the lp:duplicity branch. It seems that this was introduced in revision 783.