I think this is to do with NW.js 0.12 upgrades. The data folder NW.js 0.12 uses seems to have been in a different format to the one NW 0.13 uses, so if you in-place upgrade an app then it uses the 0.12 data folder in a 0.13 app and that seems to cause some weird issues (mostly just ghost processes, but I've seen one or two other related issues). Renaming the project causes it to start using a new empty data folder (because the data folder name is based on the project name). This fixes it and also explains why I can't reproduce the problem, because I'm just testing fresh 0.13 apps which work fine. Either way, it's a NW.js issue so it would probably be better to take this to the NW.js issue tracker, but we'd probably need a good repro for the NW.js devs. So, is anyone able to make a repro for this based on running a NW.js 0.12 app and then updating it to 0.13?
I started dissecting my project to see if I could create a capx for a bug. I renamed the project, then I removed all my sounds, and the Audio plug as I was planning to redoing all that anyway.
I exported it, and both 32, and 64 bit did not have the ghost process.
I then added one sound back with the Audio plug with an event to play it.*
No extra process was there after I tested that export.
*I noted that there were still references to the deleted sounds in the event commands.
No I did not close C2 before doing this.