ADBD Has Crashed

N3rdTek

type: crash
osVersion: google/panther/panther:14/UQ1A.231205.015/2023120800:user/release-keys
uid: 2000 (u:r:adbd:s0)
cmdline: /apex/com.android.adbd/bin/adbd --root_seclabel=u:r:su:s0
processUptime: 510s

abortMessage: failed to delete fd 21 from JDWP epoll fd: Bad file descriptor

signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: jdwp control

backtrace:
    /apex/com.android.runtime/lib64/bionic/libc.so (abort+164, pc 62e64)
    /apex/com.android.adbd/lib64/libbase.so (android::base::DefaultAborter(char const*)+12, pc 368bc)
    /apex/com.android.adbd/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+80, pc 38730)
    /apex/com.android.adbd/lib64/libbase.so (android::base::LogMessage::~LogMessage()+352, pc 37c30)
    /apex/com.android.adbd/bin/adbd (adbconnection_listen(void (*)(int, ProcessInfo))+1620, pc c5154)
    /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> >, init_jdwp()::$_0> >(void*)+168, pc c3928)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc cf9ec)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 64730)

other8026

N3rdTek looks like you have this issue: https://github.com/GrapheneOS/os-issue-tracker/issues/2724

N3rdTek

other8026
If I am understanding this correctly and bear with me cuz it seems they just go in circles; this is or was Epstein bug however there was no interface present to be able to display this until the latest A14 update. Since there is now an interface to be able to show this error people are now seeing it but it is not directly indicative of any tampering, root, or corrupt OS files and not inherently related to shizuku itself?

other8026

N3rdTek I don't know. Your issue looked to be the same so I just linked the issue from the tracker. I don't really know what the cause is. You can see other issues reference that one. It seems the project is just using the issue I linked to to track an issue with ADB that is affecting more than just Shizuku users.

Also, while reading through that issue, make sure you pay close attention to who is marked as a "member". Not sure if what the others are saying is correct or not.

N3rdTek

other8026 thank you for your references and URL source

hemlockiv

I get the same crash reports every so often. Using Shizuku.

hemlockiv

The weird thing is, when this crash happens adbd service fails, but prior to Android 14, this crash was supposedly happening silently, yet I was not seeing Shizuku randomly failing...