App crashes after exiting with a "signal 6 (SIGABRT)" in RenderThread [37123764]

Obsolete

Bug

[AOSP] assigned

NeedsInfo

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Oct 18, 2016 05:57PM

This is on a nexus 5x running Nougat. It does not happen on any other phone in our lab. Also tried loading older versions of our app (from several months ago) and those versions are also now causing this error, so I know it's not something that we added to the app recently.

Somebody on Stack Overflow seems to have the same problem.

http://stackoverflow.com/questions/40096361/native-crash-of-renderthread-with-signal-6-sigabrt?newreg=8af8e2270c9b4fab8bce30f7f43149ff

*************************
First we get this:
*************************

10-18 10:42:15.415 32304-32433/com.gogobot.gogodroid.mdev E/OpenGLRenderer: Texture is using 0.00B, count = 1
OffscreenBuffer is using 0.00B, count = 0
Layer is using 0.00B, count = 1
10-18 10:42:15.416 32304-32433/com.gogobot.gogodroid.mdev A/OpenGLRenderer: Leaked 2 GPU objects!
10-18 10:42:15.424 866-18913/? I/ActivityManager: Start proc 704:com.google.process.gapps/u0a13 for content provider com.google.android.gsf/.settings.GoogleSettingsProvider
10-18 10:42:15.425 32304-32433/com.gogobot.gogodroid.mdev A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 32433 (RenderThread)

[ 10-18 10:42:15.429 364: 364 W/ ]
debuggerd: handling request: pid=32304 uid=10120 gid=10120 tid=32433

*************************
Then we get this:
*************************

10-18 10:42:15.806 715-715/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-18 10:42:15.806 715-715/? A/DEBUG: Build fingerprint: 'google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys'
10-18 10:42:15.806 715-715/? A/DEBUG: Revision: 'rev_1.0'
10-18 10:42:15.806 715-715/? A/DEBUG: ABI: 'arm64'
10-18 10:42:15.806 715-715/? A/DEBUG: pid: 32304, tid: 32433, name: RenderThread >>> com.gogobot.gogodroid.mdev <<<
10-18 10:42:15.806 715-715/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
10-18 10:42:15.825 715-715/? A/DEBUG: Abort message: 'SANDBOX: Adjust is running in Sandbox mode. Use this setting for testing. Don't forget to set the environment to `production` before publishing!'
10-18 10:42:15.825 715-715/? A/DEBUG: x0 0000000000000000 x1 0000000000007eb1 x2 0000000000000006 x3 0000000000000008
10-18 10:42:15.825 715-715/? A/DEBUG: x4 00006e6174736e69 x5 0000000000000000 x6 0000007610dbb000 x7 0000000000000000
10-18 10:42:15.825 715-715/? A/DEBUG: x8 0000000000000083 x9 ffffffffffffffdf x10 0000000000000000 x11 0000000000000001
10-18 10:42:15.825 715-715/? A/DEBUG: x12 0000000000000018 x13 0000000000000000 x14 0000000000000000 x15 0018ce134ebca82c
10-18 10:42:15.825 715-715/? A/DEBUG: x16 000000760e80fed0 x17 000000760e7b9a2c x18 0000000000000400 x19 00000075ebce64f8
10-18 10:42:15.826 715-715/? A/DEBUG: x20 0000000000000006 x21 00000075ebce6450 x22 000000000000000b x23 0000007610197040
10-18 10:42:15.826 715-715/? A/DEBUG: x24 00000000ffffffff x25 00000075d0393280 x26 7fffffffffffffff x27 00000075ee2896b0
10-18 10:42:15.826 715-715/? A/DEBUG: x28 000000760d148878 x29 00000075ebce5ae0 x30 000000760e7b6e58
10-18 10:42:15.826 715-715/? A/DEBUG: sp 00000075ebce5ac0 pc 000000760e7b9a34 pstate 0000000060000000
10-18 10:42:15.849 715-715/? A/DEBUG: backtrace:
10-18 10:42:15.849 715-715/? A/DEBUG: #00 pc 000000000006ba34 /system/lib64/libc.so (tgkill+8)
10-18 10:42:15.849 715-715/? A/DEBUG: #01 pc 0000000000068e54 /system/lib64/libc.so (pthread_kill+64)
10-18 10:42:15.849 715-715/? A/DEBUG: #02 pc 0000000000023ed8 /system/lib64/libc.so (raise+24)
10-18 10:42:15.849 715-715/? A/DEBUG: #03 pc 000000000001c790 /system/lib64/libc.so (abort+52)
10-18 10:42:15.849 715-715/? A/DEBUG: #04 pc 00000000000107f4 /system/lib64/libcutils.so (__android_log_assert+224)
10-18 10:42:15.850 715-715/? A/DEBUG: #05 pc 0000000000054cc0 /system/lib64/libhwui.so
10-18 10:42:15.850 715-715/? A/DEBUG: #06 pc 00000000000350f8 /system/lib64/libhwui.so
10-18 10:42:15.850 715-715/? A/DEBUG: #07 pc 00000000000328c8 /system/lib64/libhwui.so
10-18 10:42:15.850 715-715/? A/DEBUG: #08 pc 0000000000037348 /system/lib64/libhwui.so
10-18 10:42:15.850 715-715/? A/DEBUG: #09 pc 0000000000038434 /system/lib64/libhwui.so
10-18 10:42:15.850 715-715/? A/DEBUG: #10 pc 0000000000039890 /system/lib64/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+152)
10-18 10:42:15.850 715-715/? A/DEBUG: #11 pc 0000000000012460 /system/lib64/libutils.so (_ZN7android6Thread11_threadLoopEPv+272)
10-18 10:42:15.850 715-715/? A/DEBUG: #12 pc 000000000009bc4c /system/lib64/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+116)
10-18 10:42:15.850 715-715/? A/DEBUG: #13 pc 000000000006863c /system/lib64/libc.so (_ZL15__pthread_startPv+208)
10-18 10:42:15.850 715-715/? A/DEBUG: #14 pc 000000000001d9fc /system/lib64/libc.so (__start_thread+16)

Comments

nm...@gmail.com <nm...@gmail.com> #2Oct 18, 2016 08:58PM

I guess this is because packages.list now is not readable by anyone:
Android 4.0.4:
-rw-rw-r--
Android 4.3:
-rw-rw----

Please provide a way to fix or work-around it.

deleted

Restricted

0 B

[Deleted User] <[Deleted User]> #3Oct 18, 2016 09:08PM

I'm having this problem as well on my Nexus 10. Fortunately I haven't updated the Nexus 7 yet, so I can still work.

nm...@gmail.com <nm...@gmail.com> #4Oct 18, 2016 09:22PM

The /data/system/packages.list was not world-readable even in 4.2.2. Would you please 1. the Build number of your 4.3 Nexus 7, and
2. that you're invoking "adb shell run-as" for a package which is definitely installed?

ga...@gmail.com <ga...@gmail.com> #5Oct 18, 2016 09:46PM

i have this problem (run-as returns: package is unknown) on my Galaxy Nexus.
i used adb shell and run-as to download database to my PC, and now it doesn't work.

[Deleted User] <[Deleted User]> #6Oct 18, 2016 09:56PM

Same problem here. Reproduced on Nexus 7 and Nexus 4. Before the 4.3 update it worked fine.

sl...@gmail.com <sl...@gmail.com> #7Oct 18, 2016 10:42PM

Nexus 7 build number JWR66V

ar...@google.com <ar...@google.com> #8Oct 19, 2016 05:34AM

Assigned to ar...@google.com.

Same here, I have 2 Nexus 7's one upgraded (JWR66V) the other not (JDQ39); run-as only works on the older build with the same debug-build of my app.

[Deleted User] <[Deleted User]> #9Oct 19, 2016 12:30PM

Not sure if this is the same problem, but I now get a "package is unknown" error when trying to "Debug as Android Native Application" from eclipse on my Nexus 7 on 4.3.

nm...@gmail.com <nm...@gmail.com> #10Oct 19, 2016 03:41PM

Same issue on Nexus 4 on 4.3 (didn't try before updating)

sp...@gmail.com <sp...@gmail.com> #11Oct 19, 2016 04:36PM

Tried on my other Nexus 4 (not updated to 4.3) with same PC configuration, and it works, so it confirms the fact that 4.3 is the problem.

[Deleted User] <[Deleted User]> #12Oct 19, 2016 04:38PM

1. My build number is JWR66V.
2. The package was installed via adb install command and can be launched from the apps menu.

[Deleted User] <[Deleted User]> #13Oct 19, 2016 05:32PM

for now, i've rooted my phone and i'm using following script:

%adb% shell "su root cp /data/data/%PACKAGE%/databases/%DB% /sdcard/my/%DB%"
%adb% pull /sdcard/my/%DB% db

th...@gmail.com <th...@gmail.com> #14Oct 19, 2016 11:25PM

Same issue here. I had NDK debugging working fine until I upgraded my Nexus 7 to 4.3. Same build as everybody else is reporting JWRR66V. I can install/uninstall my app via adb just fine. run-as however does not work and results in the following error:

gdbserver output:
run-as: Package '<my.apps.packagename>' is unknown
Verify if the application was built with NDK_DEBUG=1

ar...@google.com <ar...@google.com> #15Oct 21, 2016 06:51AM

[Comment deleted]

ga...@gmail.com <ga...@gmail.com> #16Oct 25, 2016 08:17AM

Same issue on Nexus 4.
I did Debug as Native Application in Eclipse,
and since 4.3 update, it does not work anymore.

(NEXUS 4 / BUILD JWR66V)

ga...@gmail.com <ga...@gmail.com> #17Oct 25, 2016 09:04AM

Hello,
We are aware of the issue and working on a fix.
Once we find a workaround I will also post it here.
Sorry for an inconvenience.

Regards,

ga...@gmail.com <ga...@gmail.com> #18Oct 25, 2016 09:08AM

Same problem here. This is blocking our development, as we're trying to bring up our app on a Nexus 10. Eagerly awaiting the fix!

or...@gmail.com <or...@gmail.com> #19Oct 28, 2016 05:14PM

Soo disappointed Google. Please update the priority. this is a huge regression in behavior for Android developers.

[Deleted User] <[Deleted User]> #20Oct 29, 2016 12:20AM

Any time estimate for the fix?

ga...@gmail.com <ga...@gmail.com> #21Oct 30, 2016 10:06AM

Please raise the priority of this to high, this is by no means a small issue! Development devices like the Nexus 4 are now unfit for native development as the ndk-gdb script from your very own NDK doesn't work anymore! I wasted hours yesterday trying to find out what is going on and only found this thread by coincidence. This is extremely embarrassing for Google, really!

al...@gmail.com <al...@gmail.com> #22Oct 30, 2016 08:16PM

Hello! Same there. As others please update the priority to high. This is a big deal. ETA would be really appreciated.

be...@gmail.com <be...@gmail.com> #23Oct 31, 2016 01:52PM

adding my voice to the chorus, please raise the priority. Thanks

[Deleted User] <[Deleted User]> #24Oct 31, 2016 08:26PM

Yes, raise the priority. I needed to root my device to be able to work.
Thanks in advance

su...@gmail.com <su...@gmail.com> #25Nov 3, 2016 05:32PM

same regression on Nexus 4. Can't debug native anymore. Please fix it.

[Deleted User] <[Deleted User]> #26Nov 4, 2016 02:31PM

Priority definetely should be raised.

[Deleted User] <[Deleted User]> #27Nov 7, 2016 08:19PM

Agreed. We could really use some attention in this thread...

ja...@gmail.com <ja...@gmail.com> #28Nov 8, 2016 12:43AM

We are actively working on this issue. Please do not add further comments unless you are providing new information. This affects all devices on 4.3.

dc...@scienceprousa.com <dc...@scienceprousa.com> #29Nov 11, 2016 12:46AM

Any workaround to get out app-generated data from a 4.3 device without using run-as?

ay...@gmail.com <ay...@gmail.com> #30Nov 14, 2016 06:48PM

Nicola: yes, but only if your device is rooted.

For NDK r9:

Find this line in ndk-gdb:

run adb_cmd shell run-as $PACKAGE_NAME lib/gdbserver +$DEBUG_SOCKET --attach $PID &

replace it with these 4 lines (assuming you have $NDK defined, and assuming your target device is ARM):

run adb_cmd forward tcp:5039 tcp:5039
run adb_cmd remount
run adb_cmd push $NDK/prebuilt/android-arm/gdbserver /system/bin/gdbserver.temp
run adb_cmd shell /system/bin/gdbserver.temp --attach :5039 $PID &

I am working from memory above, didn't actually test exactly what I've written just now, so I apologize for any mistakes, but that is the general idea.

Again, this requires rooted device.

deleted

Restricted

0 B

ta...@gmail.com <ta...@gmail.com> #31Nov 16, 2016 04:46PM

Another workaround is to create a Java Server to implement what you need run-as to do. Some details for starting a gdbserver at

http://stackoverflow.com/questions/17219906/run-as-package-a-b-c-is-unknown-galaxy-s4-jellybean

nm...@gmail.com <nm...@gmail.com> #32Nov 16, 2016 09:26PM

Thanks everyone for the hints. In my case I simply had to get access to a local db so just added a share button in the menu (

http://developer.android.com/training/sharing/send.html)

nm...@gmail.com <nm...@gmail.com> #33Nov 16, 2016 09:27PM

Another workaround is to install the factory image (Android 4.3), instead of updating. Do not install the mini 4.3 update afterwards!

https://developers.google.com/android/nexus/images

*Do not forget to add NDK_DEBUG=1...

[Deleted User] <[Deleted User]> #34Nov 16, 2016 09:45PM

[Comment deleted]

ay...@gmail.com <ay...@gmail.com> #35Nov 17, 2016 09:04AM

I tried installing N5D91L after seen NManoog reporting no longer experiencing this bug. Initially I believed that the N5D91L update fixed this problem, but after 10 or more cycles of backgrounding/foregrounding the app, I experienced the issue again.

After that initial issue appeared, it was much faster to reproduce--i.e. within a single background/foreground cycle.

Here's a copy of the crash info (Nexus 5X, N5D91L):

Fatal signal 6 (SIGABRT), code -6 in tid 15612 (RenderThread)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
'google/bullhead/bullhead:7.0/N5D91L/3425233:user/release-keys'
'rev_1.0'
'arm'
RenderThread >>> com.myawesomeapp <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
'Leaked 2 GPU objects!'
r0 00000000 r1 00003cfc r2 00000006 r3 00000008
r4 cc4f4978 r5 00000006 r6 cc4f4920 r7 0000010c
r8 cc4f4780 r9 00000000 sl ea4607e4 fp ea4607e0
ip 0000000b sp cc4f4300 lr eba3e537 pc eba40d94 cpsr 20010010

backtrace:
#00 pc 00049d94 /system/lib/libc.so (tgkill+12)
#01 pc 00047533 /system/lib/libc.so (pthread_kill+34)
#02 pc 0001d885 /system/lib/libc.so (raise+10)
#03 pc 000193d1 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 00017014 /system/lib/libc.so (abort+4)
#05 pc 0000c2c9 /system/lib/libcutils.so (__android_log_assert+112)
#06 pc 0003ae5f /system/lib/libhwui.so
#07 pc 00025893 /system/lib/libhwui.so
#08 pc 00023eb9 /system/lib/libhwui.so
#09 pc 00026841 /system/lib/libhwui.so
#10 pc 000270db /system/lib/libhwui.so
#11 pc 00028105 /system/lib/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+80)
#12 pc 0000e349 /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+140)
#13 pc 00063fc1 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+80)
#14 pc 00047003 /system/lib/libc.so (_ZL15__pthread_startPv+22)
#15 pc 00019e1d /system/lib/libc.so (__start_thread+6)

de...@gmail.com <de...@gmail.com> #36Nov 17, 2016 02:56PM

Could somebody from Google explain what is happening with this issue (and why it has been closed) What does "Future Release" mean? As far as I understand native debugging is no longer possible with 4.3, how is this not a critical bug?

nm...@gmail.com <nm...@gmail.com> #37Nov 18, 2016 04:53PM

This issue has been fixed in the master branch of Android, but is not yet available in a packaged release. Workarounds have already been suggested in the bug, in particular,

comment #32

nm...@gmail.com <nm...@gmail.com> #38Nov 18, 2016 04:53PM

I wasn't aware that was a verified work-around (flashing the factory image), seems to work. Thanks!

bd...@gmail.com <bd...@gmail.com> #39Nov 24, 2016 04:41PM

The "FutureRelease" status means the issue has been resolved internally, and the result will be available in a future release of Android.

bd...@gmail.com <bd...@gmail.com> #40Nov 24, 2016 04:46PM

For what it's worth, making run-as set-uid root (as it once was) again will also address the issue.

1. remount /system rw
2. chmod 4750 /system/bin/run-as
3. remount /system ro
4. enjoy debugging native code

ga...@gmail.com <ga...@gmail.com> #41Nov 25, 2016 04:39PM

[Comment deleted]

ca...@thewelcomepeople.com <ca...@thewelcomepeople.com> #42Nov 26, 2016 01:06PM

[Comment deleted]

nm...@gmail.com <nm...@gmail.com> #43Nov 26, 2016 01:15PM

Thanks Josh!
I had a hard time figuring out how to run those commands. I tinkered around and finally got it.

For rooted devices running a custom recovery:

- reboot to recovery
- find the mount system and check it
- open a terminal and type: adb shell
- type: chmod 4750 /system/bin/run-as
- uncheck the System mount and reboot!

nm...@gmail.com <nm...@gmail.com> #44Dec 15, 2016 05:18PM

im trying to do this fix on a rooted nexus 4 but i get insufficient permissions when i try to run adb shell when the phone is in recovery. im running a custom recovery
anyone has any idea on how to fix that?

dc...@scienceprousa.com <dc...@scienceprousa.com> #45Dec 15, 2016 09:49PM

Try typing "adb root" in the command line before doing the fix. If it works, you will be root directly (no need for the su command).

ku...@gmail.com <ku...@gmail.com> #46Dec 15, 2016 09:57PM

i still get "error: insufficient permissions for device" when i try to run adb anything when the phone is in recovery

[Deleted User] <[Deleted User]> #47Dec 16, 2016 08:39AM

I just restored my device to 4.3 without the mini update and it worked

ju...@gmail.com <ju...@gmail.com> #48Jan 7, 2017 01:52AM

We tried the steps in #41 on a rooted Galaxy S4 but now the application fails to launch from Eclipse (Debug As Native Android Application) with this message:

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:5039
Error message from debugger back end:
Remote communication error. Target disconnected.: No error.
Remote communication error. Target disconnected.: No error.

be...@gmail.com <be...@gmail.com> #49Feb 2, 2017 03:01PM

eodabash - non-AOSP devices aren't supported in this bug tracker at all. It's simply impossible to know exactly what an OEM might have broken with all of their changes.

BTW. I've confirmed that flashing the factory image works as a workaround for this issue too. It's probably the preferred method to using the steps I put in #41.

ma...@gmail.com <ma...@gmail.com> #50Mar 27, 2017 07:18AM

The source code for Android 4.4 was released yesterday. For those of you interested, here are the patches which resolve this bug:

https://android.googlesource.com/platform/bootable/recovery/+/5dbdef0e5b8a841fadc64d016d10ce81a962b284

https://android.googlesource.com/platform/bootable/recovery/+/e461251e2caa5561cf6a315bffaebfd4eb896b1d

https://android.googlesource.com/platform/cts/+/1f0753d1e6ccd7a894498da40fa2448d831562df

jo...@gmail.com <jo...@gmail.com> #51Mar 27, 2017 07:27AM

oops, forgot one.

https://android.googlesource.com/platform/build/+/0eb17d944704b3eb140bb9dded299d3be3aed77e

[Deleted User] <[Deleted User]> #52Mar 27, 2017 09:59AM

Thanks Nick!

bh...@gmail.com <bh...@gmail.com> #53Mar 27, 2017 10:03AM

Great that it has been resolved in 4.4 but since Google is not allowing my Nexus Galaxy to be upgraded, I'm stuck on 4.3 So it would be very nice if a 4.3 fix will be released also. I'm not in the position to buy a new device every time. Thanks you.

[Deleted User] <[Deleted User]> #54Apr 4, 2017 11:21AM

For 4.3, you can use the workaround suggested in

comment #32

r....@gmail.com <r....@gmail.com> #55Apr 11, 2017 11:25AM

For #41 and #44 this is not working at my Samsung Note 2 (Android 4.3) - permission is changed, you can run run-as by normal user but debugger is still not working. Here if You can't run adb root and adb remount you can try such solution:

http://stackoverflow.com/questions/10294808/android-mount-the-filesystem-with-write-permission .

In my case update to 4.4.2

http://true-android.blogspot.com/2013/12/update-galaxy-note-2-n7100-to-android.html?m=1 resolved problem with native debuging.

ds...@gmail.com <ds...@gmail.com> #56Apr 20, 2017 10:33AM

To adb gdb working on nexus 4, based on previous emails, I see we have to flash 4.3 image. Is it mandatory to move back to 4.3 ? or is the bug fixed on 4.4.2 (KOT49H) too?
I currently have 4.4.2 OTA upgraded and I can't run adb gdb.

gr...@gmail.com <gr...@gmail.com> #57Apr 28, 2017 08:51AM

This bug is fixed on the 4.4.2 OTA. You don't need to downgrade to 4.3.

If you can't run gdb, you should file a new bug. It's likely unrelated to this issue.

rr...@gmail.com <rr...@gmail.com> #58May 15, 2017 04:58PM

Same issuo on samsung galaxy S3

[Deleted User] <[Deleted User]> #59Jun 9, 2017 09:56AM

Finally I can debug native code with VisualGDB on Samsung Note III Android 4.3!!!!!

So I decided to share my one week hell with OTHER developers.

The reason behind all this are definitely permissions to directories and files in kernel.

So for this fix to work you really need to have rooted device to change permissions on folders and files.

1) You have to change permissions on run-as file in /system/bin folder by following these commands
adb -s <your device id> shell
su
mount -o rw,remount /system
chmod 4750 /system/bin/run-as
mount -o ro,remount /system
In the end run-as has rwsr-x--- permissions, owner is root, group is shell

2) Make sure /data folder has rwxrwx--x permissions, owner system, group system
3) Make sure /data/data folder has rwxrwx--x permissions, owner system, group system
4) Make sure /data/data/<packagename> folder has rwxrwx--x permissions, owner is uid from packages.list, group is uid from packages.list

In my case I did not have to change any permissions to packages.list file because run-as temporarily switches effective GID to allow read the packages file and also
8Kb is not the case, because run-as reads all the lines from packages.list until it finds package provided by arguments.

example from my packages.list
com.example.native_activity 10234 1 /data/data/com.example.native_activity default

package name: com.example.native_activity
uid: 10234
debuggable: 1
directory path: /data/data/com.example.native_activity
some info: default

uid is used for checking user permissions on /data/data/com.example.native_activity directory

I hope these steps help others too.

va...@gmail.com <va...@gmail.com> #60Jul 10, 2017 06:19AM

Experiencing the same issue for Android 4.4.2 on Samsung Galaxy S4. Build number KOT49H.
Has the issue reappeared?

[Deleted User] <[Deleted User]> #61Jul 17, 2017 10:00PM

"Experiencing the same issue for Android 4.4.2 on Samsung Galaxy S4. Build number KOT49H."

I am also seeing this issue on Samsung Galaxy S4 with both Android 4.3 and Android 4.4.2. If anybody can find an appropriate Samsung-specific issue tracking location for this issue, please do link to it here!

tj...@tiqets.com <tj...@tiqets.com> #62Jul 19, 2017 11:43AM

Posted on the Samsung developer forum:

http://developer.samsung.com/forum/thread/native-debugging-still-broken-on-galaxy-devices/202/258621

co...@blurry-app.com <co...@blurry-app.com> #63Jul 28, 2017 04:39PM

[Comment deleted]

js...@gmail.com <js...@gmail.com> #64Jul 31, 2017 01:06PM

In the process of trying to resolve this issue on a Samsung S4, I ended up doing a recovery at 4.4.2, and it all started working. Go figure!

So this issue appears to have resolved in Android 4.4.2 on Samsung devices, as well as on Nexus devices.

ap...@gmail.com <ap...@gmail.com> #65Aug 1, 2017 08:30AM

Wanted to add on to this in case anyone else has run out of hair to pull after experiencing this bug.

I was experiencing the issue even though my phone was updated to 4.4.2 months ago. This was particularly aggravating because everywhere I looked, I would find other people celebrating the fact that the 4.4.2 update fixed everything for them.

It turns out reinstalling 4.4.2 and wiping all data on the phone is the answer, but you can't just do that from the recovery image already present on the phone; the bug will just remain.

I had to download a dump of the exact version of 4.4.2 used by my mobile provider for my phone model from some shady website (same exact build number / baseband version / ISP code), and flash it from Download mode. Then, when I rebooted and reinstalled, native debugging simply worked.

So, just to be clear, for some reason, if you HAD a bugged version before and you updated to 4.4.2 through your mobile provider ("OTA"), it's possibly still affected by this particular issue, and the only way to fix it is to reflash -- the procedure is the same as a downgrade.

[Deleted User] <[Deleted User]> #66Aug 2, 2017 08:45AM

Comment #32

already mentioned that flashing a factory image (instead of updating) solves the issue.

ks...@gmail.com <ks...@gmail.com> #67Aug 24, 2017 03:55AM

No, #32 says to roll back to factory 4.3, before the bug was introduced, and turn off updates. That's not what you should do if you find that 4.4.2 is still affected.

[Deleted User] <[Deleted User]> #68Sep 21, 2017 02:47PM

That's not how I'm reading #32 (or this bug in general). AFAIU, the bug was introduced in 4.3, but only surfaces if you did and (OTA) update instead of a factory image flash. If you find 4.4.2 still affected, this only means that you did OTA updates (e.g. 4.2.2 -> 4.3 -> 4.4 -> 4.4.2) all the time. Flashing a factory image of 4.4.2 fixes the issue just like flashing a 4.3 factor image would have.

nc...@gmail.com <nc...@gmail.com> #69Nov 29, 2017 11:10AM

Are you saying you knew about this before I posted? I'm pretty sure this is new information, especially when you read #58, which seems to indicate the opposite of what you understand about this bug.

jt...@googlemail.com <jt...@googlemail.com> #70Nov 29, 2017 04:08PM

Well, maybe it's too much to say that I knew about it before you posted, but being aware of this bug I would definitely have tried flashing a factory image anyway. #58 indeed sounds as if updating to 4.4.2 OTA would fix the issue if it appeared on your device before. But maybe it only means that 4.4.2 OTA, unlike previous OTA updates, will not *introduce* the issue anymore. But that's my personal speculation.

pr...@gmail.com <pr...@gmail.com> #71Dec 17, 2017 01:27PM

Android 4.4.2, Samsung Galaxy S4, the same issue. It looks like Google doesn't care, because I see that the first message on this thread is from 2013, and issue is still here. I bought device specifically for development, and I can not develop with it.

nc...@gmail.com <nc...@gmail.com> #72Dec 17, 2017 02:03PM

You must complain about Samsung, not Google.

Google fixed it months ago.

sr...@gmail.com <sr...@gmail.com> #73Jan 3, 2018 02:10AM

[Comment deleted]

ds...@gmail.com <ds...@gmail.com> #74Jan 13, 2018 05:39AM

Well, unlike iPhone, Android doesn't have support. First of all, I think most customers think about Android as about Google child, and when Google says that it is not his responsibility to fix bugs, it is bad news. If not Google, than who has to fix Android bugs?

[Deleted User] <[Deleted User]> #75Jan 31, 2018 07:57PM

Basically you have a Samsung's fork of Android OS. Maybe they haven't applied that patch or maybe they have broken something else there. If you want vanilla Android, buy Nexus series. As was said, the bug *is* fixed. All's good on my Nexus 4 and Nexus 7.

[Deleted User] <[Deleted User]> #76Feb 8, 2018 11:24PM

My my Nexus 4, even after updating to 4.4.2, i can not debug native code.

On reading this thread, i thought it was due to the OTA update and so installed the factory OS from

https://developers.google.com/android/nexus/images?hl=de#nakasikot49h. The instructions for installing the factory image were taken from

https://source.android.com/source/building-devices.html.

But even after doing this, it didn't work. The permissions for package.list are still bad.

1|shell@mako:/ $ ls -al /data/system/packages.list
-rw-rw---- system package_info 13286 2014-05-26 19:15 packages.list

Can anyone point out what am i doing wrong?

[Deleted User] <[Deleted User]> #77Feb 9, 2018 04:37AM

I think the problem is if you OTA from 4.3 to a later version, you have the
problem.

I would build 4.4.2 from source and flash it onto your device.

after update to 4.3

installed the factory OS from

https://developers.google.com/android/nexus/images?hl=de#nakasikot49h. The
instructions for installing the factory image were taken from

https://source.android.com/source/building-devices.html.

package.list are still bad.

li...@addcn.com <li...@addcn.com> #78Feb 11, 2018 06:00AM

Re: #77

This is normal -- apps are not supposed to be able to read packages.list anymore, and that shouldn't interfere with run-as.

Note that this issue is characterized by the error message "run-as: Package '...' is unknown." If you don't get that particular message, the issue might be different.

The message can also pop-up if you forget to set the "android:debuggable" flag in the manifest -- see

http://developer.android.com/guide/topics/manifest/application-element.html.

po...@gmail.com <po...@gmail.com> #79Feb 21, 2018 04:49PM

Thanks for the clarification. I think i mixed two different issues. I was not getting "run-as: Package...." error. When i tried to debug using "Debug as native android app", i got this error:

[2014-05-27 12:00:54 - ImageCoreTest] Unable to find a compatible ABI
[2014-05-27 12:00:54 - ImageCoreTest] ABI's supported by the application: x86
[2014-05-27 12:00:54 - ImageCoreTest] ABI's supported by the device: armeabi-v7a, armeabi

This was not correct as when i run the same app, it works fine. The Application.mk file had

APP_ABI := armeabi-v7a

Please note, we also build X86 binary for faster debugging in android emulator.

However when i put "APP_ABI := armeabi-v7a" in Android.mk file, i can debug. This is not where it is supposed to be according to android docs but it works :(

Also, when we put "android:debuggable" in manifest, it gives an error that it should not be hardcoded. Even without it, debugging it working fine.

pa...@gmail.com <pa...@gmail.com> #80Mar 28, 2018 01:34PM

Hi, I've the "package in unknown" problem while trying to debug an andorid native application on a Galaxy S4 (OTA updated to 4.4.2). I' ve rooted the phone to change permissions of packages.list file to rw-rw--r but when I start "Debug as native Application" from eclipse permissions are changed back to rw-rw-------. How can I solve this? Do I have to flash back the firmware even if the phone is rooted?

wb...@gmail.com <wb...@gmail.com> #81Apr 18, 2018 07:40PM

Hi, I finally managed to solve this following Josh's clue to make run-as set-uid root.
Thanks.

po...@gmail.com <po...@gmail.com> #82May 13, 2018 07:38PM

@#81: Thanks for your comprehensive analysis!

I have a question regarding your workaround to listen to TRIM_MEMORY_COMPLETE and remove TextureViews from the view tree. How should I react when the app is resumed after I have removed the views from the view root? Do I have to manually restore the view root and if so, how do I do so? If I understand correcty, the app isn't necessarily killed after TRIM_MEMORY_COMPLETE, so it may be needed to be able to restore it. Another question would be how to find out which view is the one causing the problem. I do not use TextureViews in my app directly, so how am I able to find out which view may be the problem?

ib...@gmail.com <ib...@gmail.com> #83May 15, 2018 06:28AM

I also found this problem.It affected many users.I found it always happened low memory through logs.

ki...@gmail.com <ki...@gmail.com> #84May 23, 2018 01:18PM

run-as doesn't work after update to 5.0

[Deleted User] <[Deleted User]> #85May 29, 2018 09:17PM

That's unrelated to this bug. Feel free to file a new bug, including details such as the device you tested it on, etc... run-as works perfectly fine on Nexus devices.

ad...@meltingsource.com <ad...@meltingsource.com> #86May 30, 2018 12:39PM

Josh & Bitheads comments #44 helped me sort out this issue too on Android 4.4

ga...@gmail.com <ga...@gmail.com> #87May 30, 2018 01:20PM

Josh & Bitheads comments #44 helped me sort out this issue too on Android 4.4

wb...@gmail.com <wb...@gmail.com> #88May 31, 2018 05:30PM

It happened again, on Android 5.0.

I know this problem and even don't want to upgrade system,
but today I just carelessly touched the update button.

Samsung Galaxy S6 upgraded from 5.0 to 5.1.1 and damn!

po...@gmail.com <po...@gmail.com> #89May 31, 2018 06:10PM

Android 5.0.2 Galaxy Tab S, Model SM-T805 here, same problem.

wb...@gmail.com <wb...@gmail.com> #90Jun 1, 2018 06:33PM

Hi all,

This issue is closed. If you are currently having issues, please file a new bug.

pu...@gmail.com <pu...@gmail.com> #91Jun 27, 2018 03:21PM

in #50 How to add patch in my Samsung device Galexy 4.4.2

hu...@gmail.com <hu...@gmail.com> #92Aug 10, 2018 09:02AM

Fix the memory leaks does not help for this bug

se...@gmail.com <se...@gmail.com> #93Aug 10, 2018 12:53PM

After the analysis done by #81 (thx again) I've tried to implement a workaround by listening to TRIM_MEMORY_COMPLETE and reacting on it. Removing the ViewPager is not a possibility in my case. So what I have done: Listening to TRIM_MEMORY_COMPLETE and kill my app in case the devices Android version is 7.0 (I am only seeing the crash there) and not all of the relevant ViewPager views have been visible yet (as according to the analysis the crash shouldn't happen otherwise). I thought it would be better to just kill it and therefore preventing it from "officially crashing" and polluting my stats in Android Vitals. A complete restart without saving the current activity state and so on needs to be done anyway.
This workaround successfully prevented the crash BUT I could not use it anyway because of another problem. TRIM_MEMORY_COMPLETE is not only sent if the app is backgrounded! I reproduces many cases myself on real devices and my users had this effect to after I published the app update in Google Play where TRIM_MEMORY_COMPLETE was received by my app WHILE BEEING IN THE FOREGROUND! With my workaround this of course leads to my app bering killed (by myself) although it is still bering used. I don't know if this behavior is a bug or not but it's there and makes it impossible for me to use my current idea.

Any held or updates are very much appreciated!

la...@gmail.com <la...@gmail.com> #94Aug 21, 2018 01:10PM

android 8.0 application getting crash
Build fingerprint: 'google/angler/angler:8.0.0/OPR6.170623.019/4299446:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 25501, tid: 26158, name: Thread-66 >>> com.tru <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-21 18:32:53.162 26343-26343/? A/DEBUG: Abort message: 'invalid pthread_t 0xc79aa970 passed to libc'
r0 00000000 r1 0000662e r2 00000006 r3 00000008
r4 0000639d r5 0000662e r6 c7455788 r7 0000010c
r8 0000639d r9 ad47f138 sl a9a24c74 fp c74557dc
ip 00000000 sp c7455778 lr eec5d3b7 pc eec8d91c cpsr 200f0010
08-21 18:32:53.167 26343-26343/? A/DEBUG: backtrace:
#00 pc 0004a91c /system/lib/libc.so (tgkill+12)
#01 pc 0001a3b3 /system/lib/libc.so (abort+54)
#02 pc 0001e999 /system/lib/libc.so (__libc_fatal+24)
#03 pc 00047f23 /system/lib/libc.so (_Z23__pthread_internal_findl+82)
#04 pc 00047c49 /system/lib/libc.so (pthread_detach+4)

po...@gmail.com <po...@gmail.com> #95Aug 21, 2018 01:18PM

@#94: That is a different kind of crash! Got nothing to do with the problem discussed in this thread.

[Deleted User] <[Deleted User]> #96Sep 29, 2018 03:54PM

I have ViewPager with CameraView in first page. If first page is opened and app go to background, all right. But, if second page is opened (so, CameraView is invisible) and app go to background, then app crashed with Signal 6 in RenderThread. So, my hack:

@Override
protected void onPause() {
if(viewPager != null && viewPager.getCurrentItem() == 1) {
isCurrentPageIsSecond = true;
viewPager.setCurrentItem(0);
}
super.onPause();
}

@Override
protected void onResume() {
super.onResume();
if(viewPager != null && isCurrentPageIsSecond) {
isCurrentPageIsCollection = false;
viewPager.setCurrentItem(1);
}
}

I tested it with 'adb shell am send-trim-memory org.rxlab.photonotes COMPLETE' and it no crashes.

is...@google.com <is...@google.com> Oct 5, 2018 07:09AM

Status: New

ga...@gmail.com <ga...@gmail.com> #97Oct 5, 2018 10:38AM

Is this finally being looked at? I stopped developing for Android because of this issue. This was the last straw to make me jump to developing for iOS.

al...@gmail.com <al...@gmail.com> #98Oct 27, 2018 07:54AM

Any updates on this issue, have been facing same crash on Samsung Galaxy series with Android 7.0 and 7.1. My app has google maps, inside Viewpager. 1st activity has Viewpager with two pages one with maps and other with a list using RecyclerView. Upon clicking list item new Activity is opened and it has the option to take pictures and when camera Intent is launched after 1 or 2 secs my app crashes.

al...@gmail.com <al...@gmail.com> #99Oct 27, 2018 09:38AM

here is a backtrace that I see and play console

Samsung Galaxy S6 Edge (zeroltevzw), Android 7.0
Report 1

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> <applicationId><<<

backtrace:

#00 pc 000000000006b5b4 /system/lib64/libc.so (tgkill+8)
#01 pc 0000000000068a50 /system/lib64/libc.so (pthread_kill+64)
#02 pc 0000000000023f68 /system/lib64/libc.so (raise+24)
#03 pc 000000000001c9ec /system/lib64/libc.so (abort+52)
#04 pc 00000000000112ec /system/lib64/libcutils.so (__android_log_assert+232)
#05 pc 0000000000057700 /system/lib64/libhwui.so
#06 pc 00000000000372f4 /system/lib64/libhwui.so
#07 pc 0000000000034ad0 /system/lib64/libhwui.so
#08 pc 0000000000039620 /system/lib64/libhwui.so
#09 pc 000000000003a720 /system/lib64/libhwui.so
#10 pc 000000000003bb5c /system/lib64/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+148)
#11 pc 0000000000012488 /system/lib64/libutils.so (_ZN7android6Thread11_threadLoopEPv+272)
#12 pc 00000000000a4bb0 /system/lib64/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+116)
#13 pc 0000000000068258 /system/lib64/libc.so (_ZL15__pthread_startPv+196)
#14 pc 000000000001dc00 /system/lib64/libc.so (__start_thread+16)

al...@gmail.com <al...@gmail.com> #100Dec 3, 2018 06:43AM

any updates below is the backtrace from when device is attached to the debugger

2018-12-03 11:28:45.592 17280-17280/? A/DEBUG: Build fingerprint: 'samsung/zeroltedv/zerolte:7.0/NRD90M/G925IDVS3FRB1:user/release-keys'
2018-12-03 11:28:45.593 17280-17280/? A/DEBUG: Revision: '10'
2018-12-03 11:28:45.593 17280-17280/? A/DEBUG: ABI: 'arm64'
2018-12-03 11:28:45.593 17280-17280/? A/DEBUG: pid: 8251, tid: 8316, name: RenderThread >>> <applicationId> <<<
2018-12-03 11:28:45.593 17280-17280/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: Abort message: 'Leaked 2 GPU objects!'
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x0 0000000000000000 x1 000000000000207c x2 0000000000000006 x3 0000000000000008
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x4 0000000000000021 x5 0000000000000000 x6 000000738bbdc000 x7 0000000000000000
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x8 0000000000000083 x9 ffffffffffffffdf x10 0000000000000000 x11 0000000000000001
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x12 ffffffffffffffff x13 0000000000000000 x14 0000000000000000 x15 0034f521fa871c1b
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x16 0000007387c89ee0 x17 0000007387c335ac x18 0000000000000000 x19 00000073620824f8
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x20 0000000000000006 x21 0000007362082450 x22 000000000000000b x23 0000007389d3c008
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x24 00000073365c7760 x25 00000073873d5060 x26 000000733a24f920 x27 00000073873d5078
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: x28 7fffffffffffffff x29 0000007362081af0 x30 0000007387c30a54
2018-12-03 11:28:45.604 17280-17280/? A/DEBUG: sp 0000007362081ad0 pc 0000007387c335b4 pstate 0000000060000000
2018-12-03 11:28:45.639 17280-17280/? A/DEBUG: backtrace:
2018-12-03 11:28:45.641 17280-17280/? A/DEBUG: #00 pc 000000000006b5b4 /system/lib64/libc.so (tgkill+8)
2018-12-03 11:28:45.641 17280-17280/? A/DEBUG: #01 pc 0000000000068a50 /system/lib64/libc.so (pthread_kill+64)
2018-12-03 11:28:45.641 17280-17280/? A/DEBUG: #02 pc 0000000000023f68 /system/lib64/libc.so (raise+24)
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #03 pc 000000000001c9ec /system/lib64/libc.so (abort+52)
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #04 pc 00000000000112ec /system/lib64/libcutils.so (__android_log_assert+232)
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #05 pc 0000000000057700 /system/lib64/libhwui.so
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #06 pc 00000000000372f4 /system/lib64/libhwui.so
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #07 pc 0000000000034ad0 /system/lib64/libhwui.so
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #08 pc 0000000000039620 /system/lib64/libhwui.so
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #09 pc 000000000003a720 /system/lib64/libhwui.so
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #10 pc 000000000003bb5c /system/lib64/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+148)
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #11 pc 0000000000012488 /system/lib64/libutils.so (_ZN7android6Thread11_threadLoopEPv+272)
2018-12-03 11:28:45.643 17280-17280/? A/DEBUG: #12 pc 00000000000a4bb0 /system/lib64/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+116)
2018-12-03 11:28:45.644 17280-17280/? A/DEBUG: #13 pc 0000000000068258 /system/lib64/libc.so (_ZL15__pthread_startPv+196)
2018-12-03 11:28:45.644 17280-17280/? A/DEBUG: #14 pc 000000000001dc00 /system/lib64/libc.so (__start_thread+16)

mk...@gmail.com <mk...@gmail.com> #101Dec 10, 2018 02:48AM

Same happen in Android 7.0 for many different devices.

#00 pc 000000000004a230 /system/lib/libc.so (tgkill+12)
#01 pc 00000000000479c3 /system/lib/libc.so (pthread_kill+34)
#02 pc 000000000001d9c5 /system/lib/libc.so (raise+10)
#03 pc 0000000000019511 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 0000000000017150 /system/lib/libc.so (abort+4)
#05 pc 000000000000c5c7 /system/lib/libcutils.so (__android_log_assert+114)
#06 pc 000000000003cf15 /system/lib/libhwui.so
#07 pc 0000000000027183 /system/lib/libhwui.so
#08 pc 0000000000025761 /system/lib/libhwui.so
#09 pc 00000000000281d1 /system/lib/libhwui.so
#10 pc 0000000000028a73 /system/lib/libhwui.so
#11 pc 0000000000029aa1 /system/lib/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+80)
#12 pc 000000000000e401 /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+144)
#13 pc 000000000006afb5 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+80)
#14 pc 0000000000047493 /system/lib/libc.so (_ZL15__pthread_startPv+22)
#15 pc 0000000000019f6d /system/lib/libc.so (__start_thread+6)

al...@gmail.com <al...@gmail.com> #102Dec 10, 2018 01:13PM

android-bugreport@google.com at least provide some official response that there is an issue and whether or not its being looked up.

ho...@gmail.com <ho...@gmail.com> #103Dec 13, 2018 09:01AM

How to resolve this problem ? tks

11-27 17:31:10.942438 30334 30334 F DEBUG : ABI: 'arm64'
11-27 17:31:10.942474 30334 30334 F DEBUG : pid: 2692, tid: 3034, name: RenderThread >>> com.android.systemui <<<
11-27 17:31:10.942508 30334 30334 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
11-27 17:31:10.942559 30334 30334 F DEBUG : Abort message: 'sp<> assignment detected data race'
11-27 17:31:10.942619 30334 30334 F DEBUG : x0 0000000000000000 x1 0000000000000bda x2 0000000000000006 x3 0000000000000008
11-27 17:31:10.942656 30334 30334 F DEBUG : x4 fefeff741ebf1d7f x5 fefeff741ebf1d7f x6 fefeff741ebf1d7f x7 7f7f7f7f7fff7fff
11-27 17:31:10.942691 30334 30334 F DEBUG : x8 0000000000000083 x9 000000751fc3a588 x10 fffffff87ffffbdf x11 0000000000000001
11-27 17:31:10.942725 30334 30334 F DEBUG : x12 00000074822fae30 x13 ffffffffffffffff x14 ffffffffff000000 x15 ffffffffffffffff
11-27 17:31:10.942791 30334 30334 F DEBUG : x16 000000751fc712b0 x17 000000751fbaf3d8 x18 00000074822fa61a x19 0000000000000a84
11-27 17:31:10.942833 30334 30334 F DEBUG : x20 0000000000000bda x21 0000000000000083 x22 00000074808b3ca0 x23 00000074808b3cb8
11-27 17:31:10.942873 30334 30334 F DEBUG : x24 000000749e8f7310 x25 00000074809b9760 x26 000000747b5603e0 x27 431bde82d7b634db
11-27 17:31:10.942912 30334 30334 F DEBUG : x28 0000000000000000 x29 00000074822fad50
11-27 17:31:10.942946 30334 30334 F DEBUG : sp 00000074822fad10 lr 000000751fba3b90 pc 000000751fba3bbc
11-27 17:31:10.998488 30334 30334 F DEBUG :
11-27 17:31:10.998488 30334 30334 F DEBUG : backtrace:
11-27 17:31:10.998566 30334 30334 F DEBUG : #00 pc 0000000000021bbc /system/lib64/libc.so (abort+124)
11-27 17:31:10.998601 30334 30334 F DEBUG : #01 pc 00000000000080f8 /system/lib64/liblog.so (__android_log_assert+296)
11-27 17:31:10.998635 30334 30334 F DEBUG : #02 pc 000000000000f26c /system/lib64/libutils.so (android::sp_report_race()+28)
11-27 17:31:10.998676 30334 30334 F DEBUG : #03 pc 00000000001100d0 /system/lib64/libandroid_runtime.so (android::RootRenderNode::detachAnimators()+320)
11-27 17:31:10.998710 30334 30334 F DEBUG : #04 pc 000000000010e1a0 /system/lib64/libandroid_runtime.so (android::AnimationContextBridge::destroy()+24)
11-27 17:31:10.998746 30334 30334 F DEBUG : #05 pc 00000000005d182c /system/lib64/libhwui.so (android::uirenderer::renderthread::CanvasContext::destroy()+124)
11-27 17:31:10.998780 30334 30334 F DEBUG : #06 pc 00000000005d4c60 /system/lib64/libhwui.so (std::__1::packaged_task<void ()>::operator()()+88)
11-27 17:31:10.998816 30334 30334 F DEBUG : #07 pc 0000000000587918 /system/lib64/libhwui.so (android::uirenderer::WorkQueue::process()+168)
11-27 17:31:10.998850 30334 30334 F DEBUG : #08 pc 00000000001fd9b4 /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderThread::threadLoop()+244)
11-27 17:31:10.998884 30334 30334 F DEBUG : #09 pc 000000000000fb80 /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+280)
11-27 17:31:10.998923 30334 30334 F DEBUG : #10 pc 000000000008495c /system/lib64/libc.so (__pthread_start(void*)+36)
11-27 17:31:10.998961 30334 30334 F DEBUG : #11 pc 00000000000234bc /system/lib64/libc.so (__start_thread+68)

al...@gmail.com <al...@gmail.com> #104Jan 14, 2019 06:40AM

any solution??

an...@gmail.com <an...@gmail.com> #105Jan 14, 2019 07:19AM

I was getting this issue in my Samsung Galaxy J7 2016 (Nougat). But upgrading to Oreo fixed this for me.
You can see [here] (

https://stackoverflow.com/questions/53558154/sigabrt-crash-in-samsung-devices) that pattern is common with samsung device and API 7.

mi...@gmail.com <mi...@gmail.com> #106Apr 15, 2019 03:14AM

@#81 Thanks for your detailed analysis. Could you provide the fix change in Android O? I'm eager to learn how to fix it in system layer. Thank you very much!

hh...@gmail.com <hh...@gmail.com> #107Jun 3, 2019 01:48AM

@#81 ,Thank for your details , and the demo crash on emulator 100% 。

cc...@google.com <cc...@google.com> #108Jul 1, 2020 10:26PM

Status: Won't Fix (Obsolete)

Thank you for your feedback. Unfortunately, this issue is not reproducible with our version of the AOSP source code for Nexus/Pixel devices. Please file a bug with the respective OEM, as they are using their own customized version of the AOSP source code. This bug will be marked as Obsolete.

ji...@gmail.com <ji...@gmail.com> #109Nov 9, 2021 07:45AM

Comment has been deleted.

Message last modified on Nov 17, 2021 03:26AM

Issue 37123764

Description

Issue summary

Comments

nm...@gmail.com <nm...@gmail.com> #2Oct 18, 2016 08:58PM

[Deleted User] <[Deleted User]> #3Oct 18, 2016 09:08PM

nm...@gmail.com <nm...@gmail.com> #4Oct 18, 2016 09:22PM

ga...@gmail.com <ga...@gmail.com> #5Oct 18, 2016 09:46PM

[Deleted User] <[Deleted User]> #6Oct 18, 2016 09:56PM

sl...@gmail.com <sl...@gmail.com> #7Oct 18, 2016 10:42PM

ar...@google.com <ar...@google.com> #8Oct 19, 2016 05:34AM

[Deleted User] <[Deleted User]> #9Oct 19, 2016 12:30PM

nm...@gmail.com <nm...@gmail.com> #10Oct 19, 2016 03:41PM

sp...@gmail.com <sp...@gmail.com> #11Oct 19, 2016 04:36PM

[Deleted User] <[Deleted User]> #12Oct 19, 2016 04:38PM

[Deleted User] <[Deleted User]> #13Oct 19, 2016 05:32PM

th...@gmail.com <th...@gmail.com> #14Oct 19, 2016 11:25PM

ar...@google.com <ar...@google.com> #15Oct 21, 2016 06:51AM

ga...@gmail.com <ga...@gmail.com> #16Oct 25, 2016 08:17AM

ga...@gmail.com <ga...@gmail.com> #17Oct 25, 2016 09:04AM

ga...@gmail.com <ga...@gmail.com> #18Oct 25, 2016 09:08AM

or...@gmail.com <or...@gmail.com> #19Oct 28, 2016 05:14PM

[Deleted User] <[Deleted User]> #20Oct 29, 2016 12:20AM

ga...@gmail.com <ga...@gmail.com> #21Oct 30, 2016 10:06AM

al...@gmail.com <al...@gmail.com> #22Oct 30, 2016 08:16PM

be...@gmail.com <be...@gmail.com> #23Oct 31, 2016 01:52PM

[Deleted User] <[Deleted User]> #24Oct 31, 2016 08:26PM

su...@gmail.com <su...@gmail.com> #25Nov 3, 2016 05:32PM

[Deleted User] <[Deleted User]> #26Nov 4, 2016 02:31PM

[Deleted User] <[Deleted User]> #27Nov 7, 2016 08:19PM

ja...@gmail.com <ja...@gmail.com> #28Nov 8, 2016 12:43AM

dc...@scienceprousa.com <dc...@scienceprousa.com> #29Nov 11, 2016 12:46AM

ay...@gmail.com <ay...@gmail.com> #30Nov 14, 2016 06:48PM

ta...@gmail.com <ta...@gmail.com> #31Nov 16, 2016 04:46PM

nm...@gmail.com <nm...@gmail.com> #32Nov 16, 2016 09:26PM

nm...@gmail.com <nm...@gmail.com> #33Nov 16, 2016 09:27PM

[Deleted User] <[Deleted User]> #34Nov 16, 2016 09:45PM

ay...@gmail.com <ay...@gmail.com> #35Nov 17, 2016 09:04AM

de...@gmail.com <de...@gmail.com> #36Nov 17, 2016 02:56PM

nm...@gmail.com <nm...@gmail.com> #37Nov 18, 2016 04:53PM

nm...@gmail.com <nm...@gmail.com> #38Nov 18, 2016 04:53PM

bd...@gmail.com <bd...@gmail.com> #39Nov 24, 2016 04:41PM

bd...@gmail.com <bd...@gmail.com> #40Nov 24, 2016 04:46PM

ga...@gmail.com <ga...@gmail.com> #41Nov 25, 2016 04:39PM

ca...@thewelcomepeople.com <ca...@thewelcomepeople.com> #42Nov 26, 2016 01:06PM

nm...@gmail.com <nm...@gmail.com> #43Nov 26, 2016 01:15PM

nm...@gmail.com <nm...@gmail.com> #44Dec 15, 2016 05:18PM

dc...@scienceprousa.com <dc...@scienceprousa.com> #45Dec 15, 2016 09:49PM

ku...@gmail.com <ku...@gmail.com> #46Dec 15, 2016 09:57PM

[Deleted User] <[Deleted User]> #47Dec 16, 2016 08:39AM

ju...@gmail.com <ju...@gmail.com> #48Jan 7, 2017 01:52AM

be...@gmail.com <be...@gmail.com> #49Feb 2, 2017 03:01PM

ma...@gmail.com <ma...@gmail.com> #50Mar 27, 2017 07:18AM

jo...@gmail.com <jo...@gmail.com> #51Mar 27, 2017 07:27AM

[Deleted User] <[Deleted User]> #52Mar 27, 2017 09:59AM

bh...@gmail.com <bh...@gmail.com> #53Mar 27, 2017 10:03AM

[Deleted User] <[Deleted User]> #54Apr 4, 2017 11:21AM

r....@gmail.com <r....@gmail.com> #55Apr 11, 2017 11:25AM

ds...@gmail.com <ds...@gmail.com> #56Apr 20, 2017 10:33AM

gr...@gmail.com <gr...@gmail.com> #57Apr 28, 2017 08:51AM

rr...@gmail.com <rr...@gmail.com> #58May 15, 2017 04:58PM

[Deleted User] <[Deleted User]> #59Jun 9, 2017 09:56AM

va...@gmail.com <va...@gmail.com> #60Jul 10, 2017 06:19AM

[Deleted User] <[Deleted User]> #61Jul 17, 2017 10:00PM

tj...@tiqets.com <tj...@tiqets.com> #62Jul 19, 2017 11:43AM

co...@blurry-app.com <co...@blurry-app.com> #63Jul 28, 2017 04:39PM

js...@gmail.com <js...@gmail.com> #64Jul 31, 2017 01:06PM

ap...@gmail.com <ap...@gmail.com> #65Aug 1, 2017 08:30AM

[Deleted User] <[Deleted User]> #66Aug 2, 2017 08:45AM

ks...@gmail.com <ks...@gmail.com> #67Aug 24, 2017 03:55AM

[Deleted User] <[Deleted User]> #68Sep 21, 2017 02:47PM

nc...@gmail.com <nc...@gmail.com> #69Nov 29, 2017 11:10AM

jt...@googlemail.com <jt...@googlemail.com> #70Nov 29, 2017 04:08PM

pr...@gmail.com <pr...@gmail.com> #71Dec 17, 2017 01:27PM

nc...@gmail.com <nc...@gmail.com> #72Dec 17, 2017 02:03PM

sr...@gmail.com <sr...@gmail.com> #73Jan 3, 2018 02:10AM

ds...@gmail.com <ds...@gmail.com> #74Jan 13, 2018 05:39AM

[Deleted User] <[Deleted User]> #75Jan 31, 2018 07:57PM

[Deleted User] <[Deleted User]> #76Feb 8, 2018 11:24PM

[Deleted User] <[Deleted User]> #77Feb 9, 2018 04:37AM