Rob Leslie wrote:
On Sep 26, 2007, at 2:55 PM, Niels Roosen wrote:
I will post the relevant code tomorrow, should I do that as attachment or inline?
Either is fine unless it's long, in which case attachment is probably preferred.
You're not going to believe this, but I seem to have solved the problem. While scrutinizing the relevant code for posting I discovered a rather odd construct in my code (don't know why I didn't see that before) and after some more investigation I discovered that I was lying earlier. In the initialization function (which is also responsible for calling the mad_*_finish() functions if necessary) the condition for actually calling the cleanup functions was not working at all! This was because I mixed up something during development and clearly never tested this properly. So I fixed that and didn't get -any- references to lost memory in libmad anymore \o/.
Anyway, to summarize: yet another case of tunnel vision, so you try to explain your problem to someone else and during that process find out what is going wrong. So thanks nevertheless, I guess I needed this :-)
So I humbly apologize for being such a retard. Nevertheless, mad rocks my socks, it is fast and reliable unlike the mpg123 decoder which often fails to synchronize frames, miserably failing to decode an entire stream... :-)
Cheers,
Niels