Oh, I thought it was related, my bad. Our builds have been working up through 0.9.0, so it's new to 0.9.1. I've just switched back to 0.9.0 for now.
-Daniel On Wed, Mar 19, 2014 at 11:21 AM, Xavier Ducrohet <[email protected]> wrote: > Did that happen before, using 0.9.0? > > This is in a different build step, so I'm not sure how it would be related > to the png processor. > > > On Wed, Mar 19, 2014 at 9:08 AM, Daniel Lew <[email protected]> wrote: > >> I'm also getting issues with the new 0.9.1 aapt, but setting that >> command doesn't seem to fix anything. Here's a gist of the error: >> https://gist.github.com/dlew/6cbe4a92d20ef49e7270 >> >> I tested 0.9.1 on a different project and it worked just fine, so it's >> something about this particular project it doesn't like. >> >> -Daniel >> >> >> On Wednesday, March 19, 2014 10:47:30 AM UTC-5, Xavier Ducrohet wrote: >> >>> 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. >> > > > > -- > 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 a topic in the > Google Groups "adt-dev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/adt-dev/2yaMkhp9wU8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
