Debugging Android 2.3 browser crashes

Question

Recently, I've been trying to find (and hopefully, fix) frequent Android 2.3 browser crashes that affect the SB Nation blog network. Users will navigate to page and it will appear to load, and then about when you'd expect the DOM complete to fire, the browser appears to forcibly close and you are kicked to the home screen. This doesn't happen on every page load, so if you open the browser and try again, it will often load fine.

I have recreated the issue multiple times on my own phone, an HTC Thunderbolt (2.3.4) as well as a Droid Bionic (2.3.4). I have no Android development experience, but I assumed that hooking up the adb debugger may give me some insight into the the cause of this problem. Here are some of the logs of the crash I have captured:

• HTC Thunderbolt Logs
• Droid Bionic Logs

(I'd post some URLS on production that have caused these crashes, but I'm already at my two link limit.)

As you may notice, all the HTC logs differ, and the Bionic ones don't seem to offer much technical detail. This is the only common thread I found in all the HTC logs:

 D/skia    (14225): createPlugin (300,150) screen proportion:(w,h)=(0.813008,0.039288), content ratio:2.000000 mainUrl:http://athleticsnation.local:3000/
 D/skia    (14225): createPlugin F10 typical2 video content (300,150)/(369,3818), url=

My guess was F10 == Flash 10, but the Droid Bionic doesn't even have Flash installed, so I'm not convinced that is the cause.

At any rate, I'm at a loss for theories on what is causing these crashes. Is there a way to get more accurate information about these crashes? Could invalid markup be causing the browser to crash? JavaScript limitations? Any help would be greatly appreciated.

Answer 1

Probably worth looking at location permissions (and exception handling) around allowed_geolocation_origins():

From HTC dump:

10: W/ContentService( 1646): binderDied() at ObserverNode name allowed_geolocation_origins