search

GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.
https://grapheneos.org/
336 stars 18 forks source link

adbd crash (segfault) #3641

Open 0x1a8510f2 opened 2 weeks ago

0x1a8510f2 commented 2 weeks ago

While attempting to connect to android studio with ABD over WiFi, via QR code:

type: crash
osVersion: google/husky/husky:14/AP2A.240605.024/2024061400:user/release-keys
uid: 2000 (u:r:adbd:s0)
cmdline: /apex/com.android.adbd/bin/adbd --root_seclabel=u:r:su:s0
processUptime: 64s

signal: 11 (SIGSEGV), code 9 (SEGV_MTESERR), faultAddr 900c162e3306fe8
threadName: adbd
MTE: enabled

backtrace:
    /apex/com.android.adbd/bin/adbd (Connection::Serial() const+12, pc 10799c)
    /apex/com.android.adbd/bin/adbd (BlockingConnectionAdapter::Stop()+824, pc 107f08)
    /apex/com.android.adbd/bin/adbd (atransport::Kick()+128, pc 109270)
    /apex/com.android.adbd/bin/adbd (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, adbd_auth_tls_handshake(atransport*)::$_0> >(void*)+324, pc 113584)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc 795dc)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68, pc 69fa4)
thestinger commented 2 weeks ago

@0x1a8510f2 Does it happen consistently, or did it only happen once?

0x1a8510f2 commented 2 weeks ago

This is my first time using ADB over WiFi on this phone, but I have had this happen twice in a row after the phone disconnected from Android Studio and I tried pairing again.

Note that this is immediately after updating the phone and app optimisation is still running in the background. Not sure if this is relevant.

The phone appears to be connected fine for now and not disconnecting, but the crash did happen repeatedly.

0x1a8510f2 commented 2 weeks ago

Just seen it happen again without the app optimisation running. The whole connection process with Android Studio also seems very flakey. In particular, sometimes I'm unable to remove the debugging authorisation (I click forget but it just stays there). Not sure if this is unique to Graphene though since I've not used the feature on stock OS before.

AaronDewes commented 1 week ago

I am also experiencing this consistently on a Pixel 8a.