summaryrefslogtreecommitdiffstats
path: root/firmware/target/hosted
diff options
context:
space:
mode:
authorMichael Sevakis <jethead71@rockbox.org>2017-10-14 05:59:09 -0400
committerMichael Sevakis <jethead71@rockbox.org>2017-10-14 06:07:09 -0400
commit81f5a225f7ce37694b7d93cc9ce20bf1fa706a3a (patch)
treed6954306d9476bce56b531048cedb9056ade142e /firmware/target/hosted
parenta8e4b3a1906f05f6ab7fc1ee94e0be513cb2c86a (diff)
downloadrockbox-81f5a225f7ce37694b7d93cc9ce20bf1fa706a3a.tar.gz
rockbox-81f5a225f7ce37694b7d93cc9ce20bf1fa706a3a.tar.bz2
rockbox-81f5a225f7ce37694b7d93cc9ce20bf1fa706a3a.zip
Fix plugin core_alloc_maximum functionality
One mustn't assume a plugin will only call plugin_get_audio_buffer one time or that the buffer_size pointer is always non-NULL. At least one plugin, pacbox, will call it each time it (re)starts audio, with a NULL param (which is intentional because it only wants to kill audio playback), and leak away all the RAM because the handle gets clobbered by further calls and the memory can't be released. Change-Id: Ic5b94dbc0277c42964ea85b4e9d0302a7c6f1fe4
Diffstat (limited to 'firmware/target/hosted')
0 files changed, 0 insertions, 0 deletions