There is a good chance that this has been fixed. Some time ago Eric has
discovered and repaired a bug in free-ing memory after selecting another
sound (which should not have been done, as the memory to hold the .wav
resource was not malloc-ed), which might very likely be responsible for
this behavior.



Reply via email to