Debian Patches
Status for shairport-sync/5.6.2-3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Register-libsoxr-s-exit-handler-before-our-own.patch | Register libsoxr's exit handler before our own libsoxr keeps a process-wide FFT cache. The first time a conversion needs it, libsoxr registers an atexit() handler that frees it. That happens after shairport-sync has registered exit_function(), usually from the soxr_time_check() thread, so at exit the cache is freed before exit_function() and exit_rtsp_listener() have stopped the threads that use libsoxr. If SIGTERM arrives during the 1.5 s soxr timing check after startup, the soxr_checker thread is still inside soxr_oneshot() and crashes reading the freed cache, and shairport-sync exits with SIGSEGV instead of cleanly. A player thread doing soxr interpolation can probably be hit the same way, depending on the order in which the handlers were registered. Do the same conversions as soxr_time_check() once in main(), before atexit(exit_function), so that libsoxr's handler is registered first and runs last. This showed up as intermittent autopkgtest failures (exit status 139 on SIGTERM) on arm64 and armhf. |
Chris Boot <bootc@debian.org> | yes | 2026-11-09 |
