Closed kierank closed 13 years ago
Thanks for the bug report. I have had a number of long-running processes that use twolame (rotter and darkice) and have not seen this problem - although it may have been introduced in a recent version.
Note that there shouldn't be any memory being allocated during the encoding stage. I would be very grateful if you could investigate this further.
I should also run a static code analysis tool over the code at some point - I am sure there are some bad things going on.
So yes, this was me being stupid.
I do plan to fix the valgrind warnings at some point.
Sorry, this bug wasn't twolame's fault.