Bug#1103296: systemd: Caught <ABRT> from our own process
Luca Boccassi
bluca at debian.org
Wed May 21 23:13:47 BST 2025
On Tue, 22 Apr 2025 06:13:48 +0000 Peter Palfrader <weasel at debian.org>
wrote:
> On Wed, 16 Apr 2025, Luca Boccassi wrote:
>
> > Control: tags -1 moreinfo
> >
> > I see there are 3 threads in the full backtrace. In the version in
> > bookworm there was still an async cleanup routine that used posix
> > threads. This is known to mix really badly with glibc's handling of
> > malloc internals, so I strongly suspect that's the issue. This was
> > replaced with using subprocesses in trixie.
> >
> > Are you able to reproduce the issue with stable-backports or
> > testing/unstable?
>
> We switched the unit file to a static user (nobody), which seems to
have
> been successful at triggering this issue. I'll see if I can
reproduce
> the bug on a less-critical system and then try with a newer systemd.
> I'll report back in either case.
It's been a month, any update?
More information about the Pkg-systemd-maintainers
mailing list