App Inspection kills package from Android Studios Dolphin [263463288]

Assigned

Bug

Status Update

No update yet.

Description

th...@gmail.com

created issue #1

Dec 23, 2022 08:13AM

Build: AI-213.7172.25.2113.9123335, 202209300301,

AI-213.7172.25.2113.9123335, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Mac OS X(aarch64) v13.0, screens 4112.0x2658.0, 5120.0x2880.0; Retina

AS: Dolphin | 2021.3.1 Patch 1
Kotlin plugin: 213-1.7.20-release-for-android-studio-AS6777.52
Android Gradle Plugin: 7.2.0
Gradle: 7.3.3
Gradle JDK: version 11.0.13
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: 3.22.1-g37088a8, from PATH: (not found)Source: send_feedback_icon

IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Description :
When opening App Inspection Tab, the current process is killed by Android Studios
Trace in adb : signal 11 (sigsegv) code 1 (segv_maperr) fault addr 0x8
When using Android Studio Chipmunk | 2021.2.1 Canary 1, the crash is not happening.
For Dolphin, RC and preview versions the app inspection kills the package.

Comments

vi...@google.com <vi...@google.com> Dec 26, 2022 06:05AM

Assigned to an...@google.com.

jl...@google.com <jl...@google.com> #2Jan 4, 2023 11:16PM

Information redacted by Android Beta Feedback.

th...@gmail.com <th...@gmail.com> #3Jan 5, 2023 09:57AM

A physical device (STB) : SDMC Connect TV de SFR
There's not more details

ch...@google.com <ch...@google.com> Jan 10, 2023 12:12PM

Reassigned to jl...@google.com.

jl...@google.com <jl...@google.com> #4Jan 10, 2023 05:10PM

Thank you. Just a few more questions:

Does your app use compose ? (if so what version of compose)
Could you attach idea.log and logcat output ?
Does is happen on other devices or only on the SDMC device ?
What API level is the SDMC device ?
Does this problem happen on an emulator as well (with the same API level as the SDMC device) ?
Is there a tombstone created ? (You should be able to find these in /data/tombstones/ in the Device Explorer tool window in Studio.)
Does the problem happen on a later version of Android Studio such as Electric Eel or Flamingo ? (can be found here: https://developer.android.com/studio/preview)

th...@gmail.com <th...@gmail.com> #5Jan 19, 2023 09:53AM

* no compose
* logs in androidstudio.txt
* Only on SDMC (tested on SagemCom it's working)
* Android 11
* Emulator is too slow for testing on this app
* No new tombstone after crash
* Not working in android studio preview

androidstudio.txt

482 KB

View

Download

jl...@google.com <jl...@google.com> #6Jan 19, 2023 06:20PM

Here is the crash: (notice the last line: Tombstone written to: /data/tombstones/tombstone_48) So apparently there is a tombstone file created.

--------- beginning of crash
01-19 10:48:42.423 32601 32693 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 32693 (arch_disk_io_3), pid 32601 (roidtv.launcher)
01-19 10:48:42.581   341   560 D libdolbyms12: scheduler_run  sch_state:1, count:219517200
01-19 10:48:42.585   981   981 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
01-19 10:48:42.588   308   308 I tombstoned: received crash request for pid 32693
01-19 10:48:42.588   981   981 I crash_dump32: performing dump of process 32601 (target tid = 32693)
01-19 10:48:42.607   981   981 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-19 10:48:42.607   981   981 F DEBUG   : Build fingerprint: 'SFR/SFR_CONNECT_TV_V3_SDMC/DV8945-KFS:11/RT/20221031:user/release-keys'
01-19 10:48:42.607   981   981 F DEBUG   : Revision: '0'
01-19 10:48:42.607   981   981 F DEBUG   : ABI: 'arm'
01-19 10:48:42.608   981   981 F DEBUG   : Timestamp: 2023-01-19 10:48:42+0100
01-19 10:48:42.608   981   981 F DEBUG   : pid: 32601, tid: 32693, name: arch_disk_io_3  >>> com.sfr.androidtv.launcher <<<
01-19 10:48:42.608   981   981 F DEBUG   : uid: 10016
01-19 10:48:42.608   981   981 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
01-19 10:48:42.608   981   981 F DEBUG   : Cause: null pointer dereference
01-19 10:48:42.608   981   981 F DEBUG   :     r0  e55f8310  r1  0000000b  r2  e4f86c90  r3  e4f86d10
01-19 10:48:42.608   981   981 F DEBUG   :     r4  e4f86d10  r5  e4f86c90  r6  e55fb578  r7  00000000
01-19 10:48:42.608   981   981 F DEBUG   :     r8  08580c20  r9  e4f86d10  r10 08581844  r11 0000000b
01-19 10:48:42.608   981   981 F DEBUG   :     ip  0857f974  sp  e4f86b60  lr  0857cecf  pc  e52968cc
01-19 10:48:42.624   346  1263 I android.hardware.bluetooth@1.0-service: wole_config_cback, status = 0, opcode=0xfe54
01-19 10:48:43.143     0     0 E         : [585404.369447@0]  usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
01-19 10:48:43.143     0     0 W         : [585404.369511@0]  usb usb2-port1: config error
01-19 10:48:43.271   981   981 F DEBUG   : backtrace:
01-19 10:48:43.272   981   981 F DEBUG   :       #00 pc 001968cc  /apex/com.android.art/lib/libart.so (art::FaultManager::HandleFault(int, siginfo*, void*)+20) (BuildId: 1c620ca3e021ad7bbeaa77ad9dc89b68)
01-19 10:48:43.272   981   981 F DEBUG   :       #01 pc 00003ecd  /system/bin/app_process32 (art::SignalChain::Handler(int, siginfo*, void*)+364) (BuildId: 39ef0132f187b3fadb08c99e947127a4)
01-19 10:48:43.273   981   981 F DEBUG   :       #02 pc 000337a0  /apex/com.android.runtime/lib/bionic/libc.so (__restore_rt) (BuildId: 2f5972775a7fc26200e46b0b35135f74)
01-19 10:48:43.273   981   981 F DEBUG   :       #03 pc 001474ba  /apex/com.android.art/lib/libart.so (art::mirror::Class::AllocObject(art::Thread*)+10) (BuildId: 1c620ca3e021ad7bbeaa77ad9dc89b68)
01-19 10:48:43.273   981   981 F DEBUG   :       #04 pc 00187173  /apex/com.android.art/lib/libart.so (art::(anonymous namespace)::ProcessEncodedAnnotation(art::(anonymous namespace)::ClassData const&, unsigned char const**) (.llvm.4213307385609005519)+1598) (BuildId: 1c620ca3e021ad7bbeaa77ad9dc89b68)
01-19 10:48:43.274   981   981 F DEBUG   :       #05 pc 0018158f  /apex/com.android.art/lib/libart.so (art::annotations::GetAnnotationForField(art::ArtField*, art::Handle<art::mirror::Class>)+266) (BuildId: 1c620ca3e021ad7bbeaa77ad9dc89b68)
01-19 10:48:43.274   981   981 F DEBUG   :       #06 pc 00393503  /apex/com.android.art/lib/libart.so (art::Field_getAnnotationNative(_JNIEnv*, _jobject*, _jclass*)+130) (BuildId: 1c620ca3e021ad7bbeaa77ad9dc89b68)
01-19 10:48:43.274   981   981 F DEBUG   :       #07 pc 000825c5  /apex/com.android.art/javalib/arm/boot.oat (art_jni_trampoline+92) (BuildId: 6ca63848c7fb35587f6067bdc3426553da20ada5)
01-19 10:48:43.274   981   981 F DEBUG   :       #08 pc 0200203d  /memfd:jit-cache (deleted) (offset 0x2000000)
01-19 10:48:43.379   341   560 D libdolbyms12: scheduler_run  sch_state:1, count:219517500
01-19 10:48:43.424   346  1263 I android.hardware.bluetooth@1.0-service: wole_config_cback, status = 0, opcode=0xfe54
01-19 10:48:43.675   901   901 I ThermalService: CPU temperatures: [53.500004]
01-19 10:48:43.679     0     0 D [585404.909125@3]  logd: logdr: UID=10016 GID=10016 PID=981 n tail=50 logMask=8 pid=32601 start=0ns timeout=0ns
01-19 10:48:43.683     0     0 D [585404.911797@3]  logd: logdr: UID=10016 GID=10016 PID=981 n tail=50 logMask=1 pid=32601 start=0ns timeout=0ns
01-19 10:48:43.979     0     0 D [585405.205779@3]  logd: logdr: UID=10016 GID=10016 PID=981 n tail=0 logMask=8 pid=32601 start=0ns timeout=0ns
01-19 10:48:43.979     0     0 D [585405.208335@3]  logd: logdr: UID=10016 GID=10016 PID=981 n tail=0 logMask=1 pid=32601 start=0ns timeout=0ns
01-19 10:48:44.023   308   308 E tombstoned: Tombstone written to: /data/tombstones/tombstone_48

jl...@google.com <jl...@google.com> #7Jan 19, 2023 06:23PM

jreck@google.com : It looks like the crash is inside ART. Can you see what may be going on ?

th...@gmail.com <th...@gmail.com> #8Jan 20, 2023 09:26AM

I have no more idea about that I give the tombstone file

tombstone_bug_app_inspection

824 KB

Download

jl...@google.com <jl...@google.com> #9Jan 20, 2023 05:44PM

Sorry, the comment in #7 was for my colleague. Thank you for the tombstone file.

I see that you are using Dolphin. Would you be willing to see if the problem is also in Flamingo: https://developer.android.com/studio/preview

I expect that the same problem will happen, since it is probably related to the device. But perhaps we get more information.

my...@google.com <my...@google.com> #10Jan 25, 2023 01:25PM

One more question, is this limited to Android 11 or is it reproducible with a later version of Android like Android 12 / 13.

th...@gmail.com <th...@gmail.com> #11Feb 1, 2023 08:36AM

Problem still happening in Flamingo.
I can't test the device with Android 12 or after.
It's working in Chipmunks.

jl...@google.com <jl...@google.com> #12Feb 1, 2023 04:21PM

OK, thank you for checking Flamingo.

Could you check how much Storage is used on the device ?
In settings there should be a Storage entry.

th...@gmail.com <th...@gmail.com> #13Feb 2, 2023 08:51AM

$ df -H
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.5G 885k 1.5G 1% /dev
tmpfs 1.5G 0 1.5G 0% /mnt
/dev/block/metadata 12M 160k 11M 2% /metadata
/dev/block/dm-0 747M 745M 0 100% /
/dev/block/oem_a 25M 25k 24M 1% /oem
overlay 942M 217M 724M 24% /system
overlay 942M 217M 724M 24% /system_ext
overlay 942M 217M 724M 24% /vendor
overlay 942M 217M 724M 24% /product
overlay 942M 217M 724M 24% /odm
tmpfs 1.5G 0 1.5G 0% /apex
tmpfs 1.5G 4.2M 1.5G 1% /odm/lib/ms12
/dev/block/dm-6 13G 4.5G 7.9G 37% /data
tmpfs 315M 0 315M 0% /data/vendor/timeshift
/dev/fuse 13G 4.5G 7.9G 37% /storage/emulated

jl...@google.com <jl...@google.com> #14Apr 3, 2023 11:18PM

Hi Thomas, What do we need to reproduce the problem ?

th...@gmail.com <th...@gmail.com> #15Apr 5, 2023 07:32AM

I don't think you can it happens only on this application which is very big. With another app, there is no problem