Control: severity -1 serious On Tue, 2014-10-21 at 14:07:48 -0400, Zack Weinberg wrote: > Package: dpkg > Version: 1.17.19 > Severity: grave > Justification: renders package unusable
It appears to work for many people, so I'd say it's not unusable. :) > During a routine upgrade I noticed dpkg appeared to have become hung. > strace revealed that upon startup it almost immediately became stuck > in a loop allocating memory. Eventually it exhausts all available RAM > (or the process memory limit, if I set one) and crashes. I attach a > complete log of 'strace dpkg -a --configure' from a run with ulimit -m > set to 128MB and ulimit -v set to 256MB, but it's happy to chew up 64GB > of RAM+swap if I let it. I also attach a tarball of /var/lib/dpkg. > > The cut-off error message passed to write() at the very end of the > trace is > > dpkg: unrecoverable fatal error, aborting: failed to allocate memory: Cannot > allocate memory > > dpkg operations that don't (explicitly or implicitly) trigger --configure > mode are apparently unaffected. > > The set of packages needing to be processed through --configure is: […] > If you need more information please let me know. And if there is any > way to manually monkeywrench the system to restore normal operations, > I would really appreciate being told about it. ;-) Ok, looking into it now. Thanks for the dpkg database, that should hopefully help reproduce it, unfortunately its size made it not appear on the dpkg-bugs mailing list. Only saw it now due to the reply to the bug report. :( Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
