https://sourceware.org/bugzilla/show_bug.cgi?id=27399
--- Comment #6 from Frank Ch. Eigler <fche at redhat dot com> --- OK, my best guess is a transient low-memory condition. Just today we found bug #27405, which can cause some impressive momentary memory binges in elfutils. Reducing concurrency is one way to limit its impact, as you found. Giving the VM more memory is another: I run it on 16GB 8CPU class VMs, scanning even many huge debuginfo files, without a complaint. It might also help reassure here is that if you let debuginfod keep going, it'll know that it didn't finish indexing those problematic files, and will just retry later. In the long term (past rescan time), such momentary ENOMEMs are not particularly harmful. I can't think of any debuginfod per se changes or bugs in effect here. Maybe scale the default concurrency more conservatively to machine RAM rather than solely CPU count? -- You are receiving this mail because: You are on the CC list for the bug.
