Hi, This is one of the worst things of Android development ever. I am facing similar problems, also most of them with SGSIII, getting OOM crashes with no apparent reason. I have run the app in several different actual devices, also different emulator instances, one of them trying to fit as closed as possible the SGSIII settings. I have reduced heap consumption to the minimal, but I am still getting these annoying errors.
Now I am considering to buy an SGSIII actual device to test it, but this is not an option in most of the cases, and it is not clear if this will solve this problem -may be only some SGSIII are affected, and the one I bought is not one of them-. I released a new version of my app last Friday with disastrous results due to this problem -thousands of uninstalls-. I have did my best since them improving a lot memory use, writting code for actively recycle bitmaps when they are not needed and thinks like that, with excellent results (in an emulator instance with same resolution, density and VM heap budget than SGS3, I got now a 40% less of peak memory consumption than before). And it is really frustrating to see that crashes continues after all that effort. We need "something" to fight these problems. Bests, 2012/11/21 Mike Adams <adams...@gmail.com> > Hi, > > I have a kind of chat and game client, it connects to a board game server > and is a tabbed android app. There is a telnet thread and it feeds > through concurrently linked queues 3 worker threads that update a game > board, a text console and i have a lists tab. > > The problem is i've had 2 users now complain that the program has crashed > on them, one said it froze his phone. I can't be clear if the program > crashed or if its something with their phones, one was a samsung s3 i think > the other some kind of acer tablet if i recall. But how would i evaluate > this? It's never crashed for me on my tablet or phone. What kind of things > could cause a crash like this but only intermittent or on certain devices > which could have to do with the resources available on the devices and mix > of what is happening on that device. One user says he always hard stops it > before running it but it still crashed on him which kind of dismisses its a > state issue with it being up to long. > > Mike > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
