Re: [Bug 1899414] [NEW] schroot fails for source chroots with 'std:bad_alloc' on groovy

Hi Alex, Looking any https://gitlab.com/codelibre/schroot/-/blame/schroot-1.6/sbuild/sbuild-util.cc#L757 and this commit:

RE: [Bug 1899414] [NEW] schroot fails for source chroots with 'std:bad_alloc' on groovy

Hi Alex,This is failing here:https://gitlab.com/codelibre/schroot/-/blob/schroot-1.6/sbuild/sbuild-util.cc#L757Is there something unusual about the group being checked?  getgrnam_r has returned ERANGE and schroot increased the buffer size to accommodate this until it ran out of memory.  The

[Bug 1899414] [NEW] schroot fails for source chroots with 'std:bad_alloc' on groovy

Public bug reported: After upgrading to groovy or installing fresh from the beta, schroot fails to enter a source: chroot with std:bad_alloc: $ schroot -c source:bionic-amd64 E: std::bad_alloc Running this with debugging symbols under gdb we get the following backtrace: amurray@slate:~$ gdb