Let’s talk about mobile crashes a moment…

So there’s 4 types of crashes within the Fennec Native world right now.

1) Crashes that occur due to the Native UI which is caught by breakpad

2) Crashes that are caught by breakpad

3) Crashes that are caught by the OS but not breakpad

4) Crashes that neither breakpad nor the Android OS catches

In all of these cases, if you run into a crashing bug within fennec having a logcat helps out a lot.  For crashes that happen in Native UI, those java crash stacks do appear in the logcat.  In the other cases, it does help sometimes to see what the logcat is spewing during the time the crash is happening.  So please please please try to use logcat and attach it to the bug.  ( http://aaronmt.com/?p=503 or just as good is downloading alogcat.  Pro tip: To get timestamps use command line : adb logcat -v time )

So let’s go back to point 1.  So if you look at a crash now within Socorro that has a java crash :

https://crash-stats.mozilla.com/report/index/009e2d28-1fef-4b63-971c-efd782120217

You can see a new field that has the Java Stack!  Yes, thanks to the socorro team and cpeterson, esp lars, and laura.  That is hotness.

Point 2 is a matter of looking at Socorro.

Point 3/4 … if it’s released out in the Android Marketplace, there’s methods of getting the crashes from there.  Otherwise : http://www.jnchen.com/blog/2011/11/updated-gdb#the__comments  I haven’t tried to setup jimdb yet  There’s other methods for nonFennec related apps.  http://stackoverflow.com/questions/601503/how-do-i-obtain-crash-data-from-my-android-application

JimDB is probably going to be my second next project to look at leisurely at home.  Currently, I want to finish getting robocop up and running and getting tests in for robocop.

Advertisements

About shizen008

Breaking things and getting in trouble for it since '74. Disclaimer: I am not responsible if I make your head explode reading this blog! The writings here are my own expression and not of any companies. I currently work on being a QA for B2G aka Firefox OS
This entry was posted in mobifx, mobile, Planet, QA, QMO, Uncategorized and tagged , , , . Bookmark the permalink.

2 Responses to Let’s talk about mobile crashes a moment…

  1. newslastweek says:

    Sadly, I see mostly 3 and 4 on nightly, is there any possibility to catch these bugs automatically (when not connect via USB or even better without manually launching a second app)?

    • shizen008 says:

      The logcat will run in the background, log, and catch the bugs. The alogcat only reads the log file from logcat. ddms (located in /tools ) when connected will show you the history as well once you plugin.

      If you do see your logcat, you will want to look for the intent of the start of the application (something along the lines of : 02-15 17:22:32.960 I/ActivityManager( 1293): Starting: Intent { act=android.intent.action.VIEW dat=about:home flg=0x10000000 cmp=org.mozilla.fennec/.App } from pid 2899 ) , and follow it down to either when the application quitting or the device rebooting, which ever comes first.

      I hope this helps.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s