[gst-devel] library functions not returning

David Schleef ds at schleef.org
Tue Feb 17 15:19:25 CET 2004


On Tue, Feb 17, 2004 at 03:17:22PM -0800, Leif Johnson wrote:
> I've found a similar issue through using sound-juicer : For the most
> part, it works wonderfully (thanks, all !) but I came across one CD that
> has a small but deep scratch on it, which froze sound-juicer because the
> underlying cdparanoia process blocked waiting for SCSI I/O.

Actually, libcdparanoia is sitting in an infinite loop, getting
errors from the device and blindly retrying.  It's a bug in
libcdparanoia.  Unfortunately, it's not easy to fix -- it basically
requires pulling libcdparanoia's API out of the stone age.

> So along Thomas' lines, is there any way
> we could modify the cdparanoia plugin so it might be more aware of
> errors like this ?

Yes, but imo it would be smarter to add such capability to GStreamer,
not individual elements.

> Or perhaps, on an application level, sound-juicer
> could use some sort of watchdog thread ?

That would be the best solution right now (for catching all
infinite loop bugs).  Next best, the cdparanoia element should
have its own watchdog, since it has known issues with infinite
loops.



dave...





More information about the gstreamer-devel mailing list