Bug#1103296: systemd: Caught from our own process

2025-04-21 Thread Peter Palfrader
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

Bug#1103296: systemd: Caught from our own process

2025-04-16 Thread Luca Boccassi
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 repl

Bug#1103296: systemd: Caught from our own process

2025-04-16 Thread Luca Boccassi
Control: severity -1 normal On Wed, 16 Apr 2025 08:38:56 + Peter Palfrader wrote: > Package: systemd > Version: 252.36-1~deb12u1 > Severity: grave > > Since upgrading from 252.33-1~deb12u1, we have systemd fall over with > | systemd[1]: Caught from our own process. > | systemd[1]: Caught ,

Bug#1103296: systemd: Caught from our own process

2025-04-16 Thread Peter Palfrader
Package: systemd Version: 252.36-1~deb12u1 Severity: grave Since upgrading from 252.33-1~deb12u1, we have systemd fall over with | systemd[1]: Caught from our own process. | systemd[1]: Caught , dumped core as pid 797507. | systemd[1]: Freezing execution. rendering the system near unusable as an