NWJS Audio Memory Leak

TetroniMike could you or anyone else who already reproduced this issue please give me the affected NW.js versions. Info about your OS would also be appreciated (e.g. Win7).

I'll check out if something can be done directly using workarounds or report it to them if it's an internal NWjs issue. Please note that I'll only try to reproduce this potential memory leak using sounds that are included in the project, since Ashley already pointed out that playing external sounds as described isn't really supported.

TheRealDannyyy, for me it's only Chrome version since 66, so NW.js since 0.30. Thank you for digging further and sorry for not being able to reproduce with a simple project. I tried many times to play lots of random sounds and check CPU usage but the problem only appears in my already big projects that worked fine before Chrome 66.

I've tried to reproduce this issue with the provided example in nw.js v0.30.0; nw.js v0.32.0; nw.js v0.33.3; nw.js v0.34.0 (beta) and could not reproduce.

Here are my steps:

1. Export project using NW.js
2. Toggle Internal Sounds Playback
3. Unload and preload multiple times
4. Toggle Internal Sounds Playback (repeat with previous step)

I also did some experiments myself to check if something goes wrong with memory management of audio files but I got no results with that either, everything works as intended with internal audio files.

If anyone has a better, more compact example project for reproduction, I'd appreciate if you could share it here. If only bigger projects are affected, it might be worth sending them privately to Ashley so that he can look into it but I doubt that the size of a project has anything to do with this.