libjhead crashed on ARM cpu with specific image [37094486]

Obsolete

Bug

Status Update

No update yet.

Description

su...@gmail.com

created issue #1

Apr 18, 2016 05:56AM

Use Zhihu (

https://play.google.com/store/apps/details?id=com.zhihu.android) or some other app open the big image in this Zhihu question

https://www.zhihu.com/question/43322214, libjhead crashed

04-18 13:38:28.031 17726 1648 F libc : Fatal signal 7 (SIGBUS), code 1, fault addr 0x9c224e19 in tid 1648 (AsyncTask #1)
04-18 13:38:28.033 216 216 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
04-18 13:38:28.033 216 216 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
04-18 13:38:28.033 216 216 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
04-18 13:38:28.087 216 216 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-18 13:38:28.087 216 216 F DEBUG : Build fingerprint: 'google/hammerhead/hammerhead:6.0.1/MMB29X/2704508:user/release-keys'
04-18 13:38:28.087 216 216 F DEBUG : Revision: '0'
04-18 13:38:28.087 216 216 F DEBUG : ABI: 'arm'
04-18 13:38:28.087 216 216 F DEBUG : pid: 17726, tid: 1648, name: AsyncTask #1 >>>

com.zhihu.android <<<
04-18 13:38:28.087 216 216 F DEBUG : signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0x9c224e19
04-18 13:38:28.124 216 216 F DEBUG : r0 9c224e19 r1 0000000c r2 0000829a r3 0000000b
04-18 13:38:28.124 216 216 F DEBUG : r4 9c224e19 r5 0000829a r6 ac351ec8 r7 9c224d88
04-18 13:38:28.125 216 216 F DEBUG : r8 00000008 r9 000000a9 sl ac352268 fp 0000000c
04-18 13:38:28.125 216 216 F DEBUG : ip ac351f30 sp 95245088 lr ac348ad9 pc ac3483b6 cpsr 600d0030
04-18 13:38:28.134 216 216 F DEBUG :
04-18 13:38:28.134 216 216 F DEBUG : backtrace:
04-18 13:38:28.135 216 216 F DEBUG : #00 pc 000023b6 /system/lib/libjhead.so (ConvertAnyFormat+133)
04-18 13:38:28.135 216 216 F DEBUG : #01 pc 00002ad5 /system/lib/libjhead.so
04-18 13:38:28.135 216 216 F DEBUG : #02 pc 00002dbd /system/lib/libjhead.so
04-18 13:38:28.135 216 216 F DEBUG : #03 pc 00003163 /system/lib/libjhead.so (process_EXIF+258)
04-18 13:38:28.135 216 216 F DEBUG : #04 pc 00004eef /system/lib/libjhead.so (ReadJpegSections+638)
04-18 13:38:28.135 216 216 F DEBUG : #05 pc 000054a1 /system/lib/libjhead.so (ReadJpegFile+68)
04-18 13:38:28.136 216 216 F DEBUG : #06 pc 00001069 /system/lib/libjhead_jni.so
04-18 13:38:28.136 216 216 F DEBUG : #07 pc 000012a5 /system/lib/libjhead_jni.so
04-18 13:38:28.136 216 216 F DEBUG : #08 pc 731e5bfd /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x1f5b000)

Comments

su...@gmail.com <su...@gmail.com> #2Apr 18, 2016 05:57AM

I have same issue, but in addition many a time, when I switch on Bluetooth, the WiFi connection drops.

su...@gmail.com <su...@gmail.com> #3Apr 18, 2016 06:03AM

There is in fact an issue with wifi on the Nexus 4. I've written it up here:

http://things-linux.blogspot.com/2013/01/do-not-write-on-board.html

su...@gmail.com <su...@gmail.com> #4Apr 18, 2016 06:44AM

Thanks... but that is not the same issue... I can leave wifi on all the time and it will never drop connection. Even when screen blanks out. The wifi will only drop when I turn on bluetooth.

so...@gmail.com <so...@gmail.com> #5Apr 27, 2016 04:01AM

The issue with bluetooth killing wifi is a known Android 4.2.1 issue. Whether or not it is related to other wifi issues has yet to be determined, since the cause of the wifi bug has not been made public. I have also seen the bluetooth killing wifi bug on My Nexus 4, all I have to do is turn on my paired Plantronics headset.

And for clarity, my wifi doesn't "drop" either. But after the screen has been blanked for about a minute, it stops communicating. A simple ping test to your N4 can verify this. If you turn the screen back on you still see the wifi icon, but it will be greyed out. After a few seconds with the screen on, it will turn blue again (and ping will again reach your device).

so...@gmail.com <so...@gmail.com> #6Apr 27, 2016 04:02AM

Yeah, I had a discussion with a level 2 Google Play support rep. They said they are aware of the issue and to please be patient for an update. I think we need to make this more publicly known so that they get on top of it...

My wifi icon is always blue (when bluetooth isn't on, that is)... even after the screen's been off for quite some time and then turn back on. Still blue...

so...@gmail.com <so...@gmail.com> #7Apr 27, 2016 12:21PM

Thanks for the update. How did you get to discuss this with a level 2 rep? Did you call Google Device support and escalate?

so...@gmail.com <so...@gmail.com> #8Apr 27, 2016 12:38PM

After a long discussion of "It must be your router..." or "It must be your bluetooth device..." or "you must have installed some app that's causing that..." or "those radios have nothing to do with each other..." I proved to the first rep that my router + bluetooth device doesn't have any problems on my Nexus 7. Then explained that I can get the same results on both Nexus 4 (dropped wifi) and Nexus 7 (perfectly working wifi) at multiple router locations - not just mine. I then proceeded to uninstall every downloadable app... still the same problem... I then reset my phone to factory settings... still the same problem... then I booted my phone in safe mode... still the same problem. She was stumped... it was clearly a Nexus 4 issue as no outside force was causing this issue.

It took all that running around to present my case to a level two. And of course... level two knew about it and said be patient...

so...@gmail.com <so...@gmail.com> #9May 9, 2016 01:53AM

Figures. I've done essentially the same thing trying to track down the wifi sleeping problem. I've RMA'd two Nexus 4's, and the third one has the identical problem as the other two. It's about time for me to call them back again.

sa...@google.com <sa...@google.com> #10Apr 25, 2020 04:53PM

Status: Won't Fix (Obsolete)

Level one said I could do a warranty replacement, but if they don't find my issue, they would charge me full price for the new Nexus. Didn't want to risk it... Just send the update!!!