Edward Shornock <[email protected]> writes: > On 10.02.2018 23:24, Debian Bug Tracking System wrote: > > * Fix "fails with "LeakSanitizer has encountered a fatal error"" > > by fixing memory leak in plugin-runner (Closes: #886595) > > For what it's worth I still see an occasional "LeakSanitizer" crash > with 1.7.18-1. I don't have any packages installed with *plymouth* in > the name. > > Please let me know what I can do to help troubleshoot this.
You could probably *avoid* the problem entirely by recompiling the program without "-fsanitize=leak". Of course, that only hides the actual memory leak, but it avoids the problem it causes. To help *finding* the memory leak, I would suggest the following: Disable all the plugins you don't use; put the following into /etc/mandos/plugin-runner.conf: --disable=askpass-fifo --disable=plymouth --disable=splashy --disable=usplash (Make sure to rebuild the initramfs image with "update-initramfs -k all -u" after changing that file.) After doing this, do you still see "LeakSanitizer" output when booting? If you do, try to disable the "password-prompt" and/or the "mandos-client" plugins as well. Note: disabling the "mandos-client" plugin will necessitate the manual typing of the password on boot, and disabling "password-prompt" plugin will rely on the Mandos client for getting the password. You could also disable them *both*, and the plugin-runner will fall back to asking for the password itself on the console. I am wondering which, if any, of these disablings will make the LeakSanitizer errors go away on your system. That would help to narrow the problem down significantly. /Teddy Hogeborn -- The Mandos Project https://www.recompile.se/mandos
signature.asc
Description: PGP signature
