First of all I want to give a big Thanks to everybody here that is working very hard for the community.
We have a game developed since last year and now, we are developing new features.
The problem is that once everything is done and “working” and ready to be uploaded, we are getting a random error:
\ Crash dump:\Build fingerprint: ‘samsung/m0xx/m0:4.1.2/JZO54K/I9300XXELLA:user/release-keys’
pid: 21723, tid: 21768, name: Thread-18076 >>> org.cocos2dx.hudrfactor <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
Stack frame #00 pc 0016a69a /data/data/org.cocos2dx.hudrfactor/lib/libgame.so (cocos2d::CCActionManager::update(float)+257)
Stack frame #01 pc 00156b9d /data/data/org.cocos2dx.hudrfactor/lib/libgame.so (cocos2d::CCScheduler::tick(float)+188)
Stack frame #02 pc 001768a9 /data/data/org.cocos2dx.hudrfactor/lib/libgame.so (cocos2d::CCDirector::drawScene()+44)
Stack frame #03 pc 00177baf /data/data/org.cocos2dx.hudrfactor/lib/libgame.so (cocos2d::CCDisplayLinkDirector::mainLoop()+50)
Stack frame #04 pc 001a35dd /data/data/org.cocos2dx.hudrfactor/lib/libgame.so (Java_org_cocos2dx_lib_Cocos2dxRenderer_nativeRender+20)
Stack frame #05 pc 0001deb0 /system/lib/libdvm.so (dvmPlatformInvoke+112)
Stack frame #06 pc 0004d103 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const**, JValue**, Method const**, Thread**)+394)
Stack frame #07 pc 00000214 /dev/ashmem/dalvik-jit-code-cache (deleted)
We are getting crazy because is a random error, we have tested in a Samsung Galaxy S I and it needs about 10 minutes to give this error , but in a Samsung Galaxy S III, the problem arise in two / three minutes …. each time in a new place.
We have been looking for a fix, but we are now desperate…
I know that probably upgrading to Cocos2d x 2.0 we can get a stable version of the game, but this is a HUGE change we think…
Please any advise, whatever you think about it, will be more than welcome, we are desperate as I said!(.
Thank you very much for your help)