Am 21. November 2024 10:55:37 MEZ schrieb reduzent@gmail.com:
Hey all
I've been running two Icecast2 streams for a few years that are fed by a Pd patch. Those patches use [readanysf~] to playback MP3 and other audio media, partially from URL. The result is sent through [mp3cast~] to an Icecast2 server.
Since a few weeks, the patch segfaults after a few hours/days of running.
Urgh. That will make debugging hard...
This is the backtrace (not much useful info, libraries from Debian seem not compiled with debug symbols):
They are compiled *with* debug symbols, but thesr are not shipped in the "normal" packages (to keep them nice and small). See https://wiki.debian.org/HowToGetABacktrace on how to install the debug symbols for a given package.
which indicates the problem is in the [readanysf~] playback and not in Pd or [mp3cast~].
Well if it happens only every few days, things might be related to thread and/or memory management, which means that the cause of the problem could be *anywhere*. But if course the backtrace is where I would start looking as well.
I plan to run those streams for some more years and am looking for a sustainable way to play back the audio files. Thus, I'm evaluating possible options:
- Fix [readanysf~] (if the problem is in readanysf~ and not in a
library)
- Switch to [mp3amp~] from unauthorized. However, it doesn't compile
with current libmpg123
I think it was just today that somebody on irc mentioned that they would not recommend using "unauthorized".
cannot compile the original sources). What does it mean for the future of the object that the external doesn't have an upstream maintainer?
That it should be moved to the "pd-externals" repository so people *can* give it some love in a discoverable place.
Before those issues arose, the streams have been running for years with minimal maintenance effort. That really speaks for Pd's quality and careful development practices. I can't quite figure out what changed in the system. I upgraded the server to Debian bookworm last year, but experience the issues only since a few weeks.
There was a bookworm point release last week, maybe this is related (in case you do regular security upgrades). Check the apt and dpkg logs...
mfg.sfg.jfd IOhannes