CocoonJS Canvas+ is no longer officially supported, in part due to the memory management problems it has.
Consider the CocoonJS WebViews instead, or Crosswalk for Android, or PhoneGap Build for iOS 8+.
Develop games in your browser. Powerful, performant & highly capable.
damainman Escualo - are either of you able to strip down a .capx to the minimum possible which still reproduces the problem? This would make it a lot easier to investigate.
Apparently Amazon Fire TV now supports HTML5 apps with support for WebGL and Gamepads:
https://developer.amazon.com/post/Tx3ALQCEOVXJBJ9/Extend-the-Reach-of-Your-HTML5-App-to-the-Living-Room.html
We don't have a Fire TV in the office right now to test with - does anyone have one and have you tried it?
Don't global layers mostly solve this?
Escualo - is there anything else in the project using the same name?
I can reproduce on iOS 8, but it looks like a browser crash, not a problem with the C2 engine. Also Windows Media Player says the resulting .m4a file is invalid as well, which probably means the encoder failed to produce a valid .m4a file. Unfortunately we don't control the .m4a encoder and due to the patent restrictions on the format it's not easy to switch to another one. So I'm afraid we have to close this as won't fix. You may be able to work around it by using a separate tool to encode the .m4a from the .wav file, then directly import the .m4a in to C2 so it doesn't convert it itself.
Closing, please follow the bug report guidelines.
makebelieve - the problem is not in C2, it's in the project. The latest C2 update made a change which exposes the problem with your project. Did you try renaming "player_1_select"? What is there in the project that is called that? I found an object but renaming it did not fix it, perhaps there's some other variable or something else with that name?
Should be fixed in the next build.
Closing as fixed by Apple in iOS 8.
Closing as probably fixed in r191 - please let me know if you still run in to any issues with r191+.
Lunatrap - you mentioned you used 250 text objects, and the fix in r191 is that there was indeed a memory leak per text object when previewing which could result in this issue, which is why I think it should now be fixed.
Fixed for next build. (Took a while but got there in the end!)
Crosswalk is a few versions behind Chrome (the browser is currently v39, I think Crosswalk is more like v36). It may be that just waiting for the next Crosswalk update will resolve this.