Bug#781844: rdiff-backup: crashed after hitting process memory limit

2021-09-28 Thread Pablo Mestre
Hi Matt Taggart Thank you very much for reporting this error. I would like to ask you if this error is still present in the most recent versions of rdiff-backup. Currently after a series of improvements and bug fixes, rdiff-backup is at version 2.0.5 [1] It would be very helpful if you checked

Bug#781844: rdiff-backup: crashed after hitting process memory limit,version graph

2020-10-14 Thread Pablo Mestre
Hi Thank you very much for reporting this error. I would like to ask you if this error is still present in the most recent versions of rdiff-backup. Currently after a series of improvements and bug fixes, rdiff-backup is at version 2.0.5 [1] It would be very helpful if you checked again if this

Bug#781844: rdiff-backup: crashed after hitting process memory limit

2015-04-19 Thread Matt Taggart
Regarding #781844, I got a chance to try booting a 686-pae kernel and it solves the problem. So I think rdiff-backup is making some sort of assumption based on the booted kernel, rather than by looking at the userspace. And then that assumption results in a memory leak. -- Matt Taggart tagg...

Bug#781844: rdiff-backup: crashed after hitting process memory limit

2015-04-03 Thread Matt Taggart
Package: rdiff-backup Version: 1.2.8-7 I am running into a situation where rdiff-backup grows in memory usage until it crashes. Client: amd64 userspace, amd64 kernel, 16gb of RAM Server: i386 userspace, amd64 kernel, 32gb of RAM Both are using rdiff-backup 1.2.8-7 and librsync 0.9.7-9 (on wheezy