I\'m having a strange problem with Android 1.6
I have an application that has a ListView (found in Activity #1).
The user can click on one of the rows in t
Dude, try to clear cache of any sort.. specially images. As you are using list view, try not to create a new view every time with respect to convertview
I was having similar problem. here is my post SIGNAL 11 SIGSEGV crash Android
This is a very low-level exception that indicates a bug in Android itself. Based on the LogCat dump, the bug may be unique to the DROID/Milestone, though I am not certain of that. If you are indeed encountering this bug on a Motorola device, I recommend posting your stack trace on the appropriate MOTODEV message board, as that will be the quickest way to get the issue investigated.
you should report native crashes like this at http://code.google.com/p/android/issues/entry (choose the "developer bug report" template). include exactly what you included here, and if you can, please include your app (or the active ingredient thereof) so we can reproduce the crash to find the problem and verify the fix.
as for the strange stack trace, it's because this is a crash in native code. google developers have the map from those "pc" (program counter) addresses to symbols, so we can work out where in the native code this happened. (Typeface_unref, as it happens, so this seems unlikely to be Droid-specific.)
[the "zombie" referred to is the crashed process. debuggerd is just telling you that it's not leaving it around for debugging --- it's clearing it away on the assumption you're a user and just want to get on with your life.]
this particular bug has already been fixed; the fix should be in the first release after 2.1.