Hello, apologies if this is the wrong place to post this. I just turned my phone back on after leaving it powered off for several hours, and got a notification that "android.hardware.bluetooth-service.mcmbtlinux has crashed". I'm not sure why I would get this error since I've had bluetooth disabled and airplane mode enabled for the past several months.

The crash log is below. Thank you in advance for any thoughts.

type: crash
osVersion: google/bluejay/bluejay:14/AP2A.240705.004/2024071200:user/release-keys
uid: 1002 (u:r:hal_bluetooth_btlinux:s0)
cmdline: /vendor/bin/hw/android.hardware.bluetooth-service.bcmbtlinux
processUptime: 0s

abortMessage: hardened_malloc: fatal allocator error: double free (quarantine)

signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: binder:808_1

backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (abort+164, pc 64a24)
/apex/com.android.runtime/lib64/bionic/libc.so (fatal_error+44, pc 4e504)
/apex/com.android.runtime/lib64/bionic/libc.so (deallocate_small+1572, pc 4bbc4)
/vendor/bin/hw/android.hardware.bluetooth-service.bcmbtlinux (android::hardware::bluetooth::hci::HciFlowControl::HciFlowControl()+36, pc 1c4e4)
/vendor/bin/hw/android.hardware.bluetooth-service.bcmbtlinux (android::hardware::bluetooth::hci::shim::Deinitialize()+104, pc 3fdc8)
/vendor/bin/hw/android.hardware.bluetooth-service.bcmbtlinux (android::hardware::bluetooth::aidl::bcmbtlinux::BluetoothHci::signal_handler(int)+116, pc 51594)
[vdso] (pc 88c)
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+4, pc cde84)
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+156, pc 7133c)
/system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+296, pc 50848)
/system/lib64/libbinder.so (android::PoolThread::threadLoop()+24, pc 50708)
/system/lib64/libutils.so (android::Thread::_threadLoop(void)+244, pc 115d4)
/apex/com.android.runtime/lib64/bionic/libc.so (
pthread_start(void)+204, pc 7679c)
/apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 67d50)

    2wnin
    Can't provide a solution, but there's an issue for this posted on the github tracker. So far, no answer seems to have been given, but worth keeping an eye on.

      Dumdum Thanks! I'll post my issue there as well.