The BIG game challenge (Ejecta memory management on iOS)

@MaorKeshet

I suggest you try CocoonJS, while it lacks memory management, it does not have this memory accumulation issue upon changing layout (other user of Ejecta have reported the same bug). So if its <200MB total with CJS, it should be ok on 512mb devices. Not ideal though.

Hopefully later this year, Phonegap + iOS8 will be great.

Neither Match or Dots) are on the heavy side of the layouts... these are the games that are less likely to crash actually [sigh]

@MaorKeshet

I suggest you try CocoonJS, while it lacks memory management, it does not have this memory accumulation issue upon changing layout (other user of Ejecta have reported the same bug). So if its <200MB total with CJS, it should be ok on 512mb devices. Not ideal though.

Hopefully later this year, Phonegap + iOS8 will be great.

Thnx Silverforce. As far as I know CocoonJS is limited to 30Mb app size. My completed app will be ~150Mb. Is there a way to wrap such large app with CocoonJS?

@MaorKeshet

I suggest you try CocoonJS, while it lacks memory management, it does not have this memory accumulation issue upon changing layout (other user of Ejecta have reported the same bug). So if its <200MB total with CJS, it should be ok on 512mb devices. Not ideal though.

Hopefully later this year, Phonegap + iOS8 will be great.

Thnx Silverforce. As far as I know CocoonJS is limited to 30Mb app size. My completed app will be ~150Mb. Is there a way to wrap such large app with CocoonJS?

If you request premium access with them, they will up the limit to 200Mb. But just in case, you cannot upload over 50Mb APK to the Google Store currently.

The memory issue is more with IOS. Seems that most Android devices run on 1gb for a longer period of than IOS has been. Seems that CJS may be worth a shot with all the optimizations that have gone on. I would suggest trying with the launcher and copying an export out.

The memory issue is more with IOS. Seems that most Android devices run on 1gb for a longer period of than IOS has been. Seems that CJS may be worth a shot with all the optimizations that have gone on. I would suggest trying with the launcher and copying an export out.

@Jayderyu My CJS build crashed upon startup so I'm not going to continue this path. Not sure what you meant about "copying the export out" though. From C2 I exported to CJS and used the cloud compiler.

[Ashley]

I took this up with Dominic (lead dev of Ejecta) and Dominic managed to identify an Ejecta bug that was causing WebGL to fail to delete textures. The patch has been submitted to the main codebase (https://github.com/phoboslab/Ejecta). Try re-downloading the files and let me know if memory management is working better.

This is great Thanks @Ashley.
I already downloaded the xcode master zip, will test and report as soon as I'm back to my desk.

I took this up with Dominic (lead dev of Ejecta) and Dominic managed to identify an Ejecta bug that was causing WebGL to fail to delete textures. The patch has been submitted to the main codebase (https://github.com/phoboslab/Ejecta). Try re-downloading the files and let me know if memory management is working better.

Excellent, glad its just a small bug and doesn't require a lot of work to fix!

Looking forward to the results @MaorKeshet !

@Ashley @jayderyu @Silverforce

I run few quick tests with the new ejecta master template. Memory engagement look very effective, I was surprised to find out that the memory usage drops occasionally even while playing a game (!)

Many thanks to Ejecta team and to Ashley

https://dl.dropboxusercontent.com/u/8918895/Screenshot%202014-06-20%2014.38.26.png