Running for example 'a2play -ddummy a2jingle.a2s' will result in a memory leak of around 270 kB (waves and other objects) when the engine state is closed. This does not happen when using a proper audio driver.
I'm suspecting this isn't directly related to the "dummy" driver, but rather an effect of running the engine state in offline mode. (No "audio thread", as that's not yet implemented in the "dummy" driver.)
Easiest way to test this is with the 'apistress' test, which uses the "dummy" driver - and BTW; indeed, the problem goes away when using the "jack" driver.
Running for example 'a2play -ddummy a2jingle.a2s' will result in a memory leak of around 270 kB (waves and other objects) when the engine state is closed. This does not happen when using a proper audio driver.
I'm suspecting this isn't directly related to the "dummy" driver, but rather an effect of running the engine state in offline mode. (No "audio thread", as that's not yet implemented in the "dummy" driver.)