Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 317 Plugins
- 70 User experience
- 75 Marketplace
- 291 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
In this Discussion
random (but early) crashes on certain devices: Fatal signal 11 (SIGSEGV) and gles_state_set_error...
keszegh
Member
I noticed that on my new phone the app (in the player apk and from eclipse as well) randomly crashes, i get the following two kinds of errors in eclipse (as there was no debug info in gideros):
06-04 14:50:18.194: A/libc(1972): Fatal signal 11 (SIGSEGV) at 0x0000000a (code=1), thread 1972
06-04 14:49:41.762: E/MALI(1415): gles_state_set_error_internal:57: GLES error code:0x502
so on my tegra2+1gb+android4.0.* device it's working without problems, also on windows player there is no problem at all but on my xperia e4g (mtk chip)+1gb+android4.4 i get the above errors
also on an lg l40 (also android 4.4) it freezes, i did not connect it to eclipse, but i assume the problem is the same.
from zbstudio i tried to debug line-by-line but in fact the error happens at different points so it its not related to a specific line.
i think it may not be even directly related to the new version of gideros, with 03.22 version it also crashed on my phone (i did not try it with eclipse).
any ideas? it's a bit frightening that on 2 devices out of 3 my game is not running. perhaps it's related to the android version?
further observations: there are some movieclips i initialize, around 10 of them, all with around 10-20 bitmaps of size ~450x250, the crash happens during this most surely - even if it varies exactly when. if i comment out this part then i can run my game and it crashes a bit later at a more or less random point soon, but i suspect it's always during when some bitmap.new() is happening.
06-04 14:50:18.194: A/libc(1972): Fatal signal 11 (SIGSEGV) at 0x0000000a (code=1), thread 1972
06-04 14:49:41.762: E/MALI(1415): gles_state_set_error_internal:57: GLES error code:0x502
so on my tegra2+1gb+android4.0.* device it's working without problems, also on windows player there is no problem at all but on my xperia e4g (mtk chip)+1gb+android4.4 i get the above errors
also on an lg l40 (also android 4.4) it freezes, i did not connect it to eclipse, but i assume the problem is the same.
from zbstudio i tried to debug line-by-line but in fact the error happens at different points so it its not related to a specific line.
i think it may not be even directly related to the new version of gideros, with 03.22 version it also crashed on my phone (i did not try it with eclipse).
any ideas? it's a bit frightening that on 2 devices out of 3 my game is not running. perhaps it's related to the android version?
further observations: there are some movieclips i initialize, around 10 of them, all with around 10-20 bitmaps of size ~450x250, the crash happens during this most surely - even if it varies exactly when. if i comment out this part then i can run my game and it crashes a bit later at a more or less random point soon, but i suspect it's always during when some bitmap.new() is happening.
Comments
i would appreciate that.
Fragmenter - animated loop machine and IKONOMIKON - the memory game
Error 502 seems to be a generic GL error, saying the some command cannot be processed, but not telling why... libc would be more instructive if only we had full backtrace.
As always in those cases, only a developer that can actually reproduce the crash may be able to fix it..
how to get libg backtrace? (sorry, i leave gideros/i use eclipse only when i must)
Fragmenter - animated loop machine and IKONOMIKON - the memory game
others do not have such problems on such devices?
i will try also some of the demo codes soon if they work well or not.
Fragmenter - animated loop machine and IKONOMIKON - the memory game
Debugging native apps with Android seems fairly complex from what I read, so to be honest I don't really know how to proceed... if someone else reading this knows better, than please share!
Despite this, I've been working on @NatWobble GPU traces on iOS and they show some incorrect GL calls. There is a small chance that fixing those may fix your issue too.
However I have started a major refactoring of OpenGL related code within gideros. OpenGL calls are currently widely spread among gideros code, and I am moving them all in a specfic part. Having GL calls concentrated will make them easier to debug/optimize. Hopefully those changes will allow a more precise GL management, but I don't expect them to be release before at least two weeks.
Fragmenter - animated loop machine and IKONOMIKON - the memory game
i think that in fact i simply ran out of memory because i loaded all the textures i need in any scene at the beginning to avoid lags but recently i've added a movieclip framebyframe animation which was too much for some of my devices.
it would be great if there would be a trackable error message in gideros if the app quits because of running out of memory, then i would have saved two days of trying to spot what exactly is the problem.
another thing i've learnt is that collectgarbage("count") gives only the non-texture memory used and application:getTextureMemory() is essential to track used memory.
i was always surprised that my app uses so low memory, and i thought that maybe it's not in kb but in mb. but in fact it was low because it did not contain the texture memory i used up - this way i could not realize that this was getting too much.
thanks for trying to help. i will let you know if i have further problems related to this topic.
Fragmenter - animated loop machine and IKONOMIKON - the memory game
Fragmenter - animated loop machine and IKONOMIKON - the memory game
thanks.
Fragmenter - animated loop machine and IKONOMIKON - the memory game