Picasso 2.5.2 SIGILL Crash

[mariusc83]

Hi Jake,

I have a problem with the new version of Picasso on some devices. Bellow you can find the stackTrace from Play Store, please let me know if I can help you with something else. Thanks!!

Revision: '0'
signal 4 (SIGILL), code 2 (ILL_ILLOPN), fault addr b7732c0d
eax 000000d3 ebx b7737f60 ecx 06be46fe edx 06be46fe
esi 7eedc3a4 edi b7f22794
xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
eip b7732c0d ebp 7df1142c esp 7df11400 flags 00210246

backtrace:
#00 pc 00001c0d /system/lib/liblog.so (__android_log_assert+125)
#01 pc 0000621e /system/lib/libstagefright_soft_h264enc.so (android::SoftAVCEncoder::internalGetParameter(OMX_INDEXTYPE, void*)+718)
#02 pc 0001af73 /system/lib/libstagefright_omx.so (android::SimpleSoftOMXComponent::getParameter(OMX_INDEXTYPE, void*)+67)
#03 pc 0001dd82 /system/lib/libstagefright_omx.so (android::SoftOMXComponent::GetParameterWrapper(void*, OMX_INDEXTYPE, void*)+34)
#04 pc 000185a4 /system/lib/libstagefright_omx.so (android::OMXNodeInstance::getParameter(OMX_INDEXTYPE, void*, unsigned int)+68)
#05 pc 000135f9 /system/lib/libstagefright_omx.so (android::OMX::getParameter(void*, OMX_INDEXTYPE, void*, unsigned int)+121)
#06 pc 000c2ae9 /system/lib/libstagefright.so (android::MuxOMX::getParameter(void*, OMX_INDEXTYPE, void*, unsigned int)+137)
#07 pc 00056f73 /system/lib/libstagefright.so (android::ACodec::setupVideoEncoder(char const*, android::sp<android::AMessage> const&)+403)
#08 pc 000579e6 /system/lib/libstagefright.so (android::ACodec::configureCodec(char const*, android::sp<android::AMessage> const&)+534)
#09 pc 0005e3ad /system/lib/libstagefright.so (android::ACodec::LoadedState::onConfigureComponent(android::sp<android::AMessage> const&)+125)
#10 pc 0005ec19 /system/lib/libstagefright.so (android::ACodec::LoadedState::onMessageReceived(android::sp<android::AMessage> const&)+121)
#11 pc 0000a358 /system/lib/libstagefright_foundation.so (android::AHierarchicalStateMachine::onMessageReceived(android::sp<android::AMessage> const&)+248)
#12 pc 0000d1ea /system/lib/libstagefright_foundation.so (android::ALooperRoster::deliverMessage(android::sp<android::AMessage> const&)+346)
#13 pc 0000b581 /system/lib/libstagefright_foundation.so (android::ALooper::LooperThread::threadLoop()+289)
#14 pc 00017c70 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+512)
#15 pc 00017e76 /system/lib/libutils.so (thread_data_t::trampoline(thread_data_t const*)+246)
#16 pc 0000bc8c /system/lib/libc.so (__thread_entry+236)
#17 pc 0003e315 /system/lib/libc.so (__pthread_clone+69)
#18 pc 00017d7f /system/lib/libutils.so
#19 pc 000a39bf [heap]
#20 pc 00092caf [heap]
#21 pc 00092a5f [heap]
#22 pc 0004b40f [heap]
#23 pc 000827ff [heap]
#24 pc 000787cf [heap]
#25 pc 0002815f [heap]
#26 pc 000262df [heap]
#27 pc 0000ef7f [heap]
#28 pc 0000de0f [heap]
#29 pc 0017104f [heap]
#30 pc 0017077f [heap]
#31 pc 00036cff [heap]

[dnkoutso]

What version is it? 2.5.1 or 2.5.2?

[mariusc83]

2.5.2

[mariusc83]

It was also present on 2.5.0, I made a new update wit 2.5.2 but I have the same problem. Should I go back to 2.4.0 for the moment ?

[mariusc83]

Any news on this issue ? I currently downgraded my project to use the 2.4.0 release and so far so good only one similar problem reported on a Motorola device. Could this be related with the fact that I am using AppSee for tracking and this API is using also some NDK libraries ? Please let me know if I can help you with other information.

[dnkoutso]

If you are still seeing the issue, it might be related. Those are really hard to figure out, and could be, although not guaranteed, unrelated to Picasso.

[mariusc83]

I was also thinking to this possibility and I just figured it out that is also the AppSee that is using NDK, I will also have a ask their opinion on this matter. Thanks for all the support and I will come with a conclusion once I will have one :).

[mariusc83]

Hi Guys,

I promised that I will come back when I will have a final conclusion. You were right the problem was not caused by Picasso API but by another Analytics API which is using NDK to record some video sessions. My apologies for all the trouble and thanks for all the help, I will close this issue now.