Well  the initial results were in from Flurry and they were not good reading. Apparently 2% of all session resulted in a force close. I call force closes either hangs or crashes and will probably slip back into that terminology sometime in this post.


Wow 2% is pretty high! It was not something I could really leave, it needed fixing. Trouble is I could not reproduce the hangs and flurry by default does not give you much to go on. I was just about to embark on a close look some large chunks of a program which would have been a time consuming job when a user emailed to say he was getting force closes and he did a series of actions that he listed. 


So Instead of being a massive task I was able to zero in on the code causing his problem and produce an update in just a couple of hours. I am hopping this one bug was the cause of many of the hangs I have been seeing.


The next couple of days should tell me if that hope is correct or not as I should see a reduction in force hangs as people upgrade. If it does not fix a significant number of the hangs I will have to go over the code very closely and see if I can spot any other problems hiding in there.


Apologies to those that have been getting those force hangs I fix all the problems I can find. 
 


Comments

Sat, 01 May 2010 11:44:54 am

Hello

I'm a content manager for the content development and distribution company Logia Group. We are currently working on a new branded Android Application store and would like to have your application published there.

Please contact me for further details.

 

Comments are closed.