Hi, I've seen another report that it's due to the new png processor. For now you can disable it with android.aaptOptions.useAaptPngCruncher = true
I would love though if you could figure out which png causes this (and send it to me, off list if needed). We have a whole suite of png tests and none of them triggers this. On Wed, Mar 19, 2014 at 8:24 AM, Christoffer Hirsimaa <[email protected]>wrote: > While developing today I noticed I can't boot my application on Galaxy > Pocket anymore. It shows the default theme of the activity (onCreate is > called but never finishes when trying to log) and no crash dialog is shown > afterwards. After an hour of head banging against the wall I found out that > it is the 0.9.1 release that causes this. The only thing that appears in > logcat is this: > > A/libc﹕ Fatal signal 11 (SIGSEGV) at 0x00000001 (code=1) > > My application has native libs but they don't even have time to attempt to > load them from what I can see in logcat. Changing back to 0.9.0 makes the > application work again and this is independent of my own code. > > Something else I can check for? Is this enough for you to find the problem? > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
