DeadlockObserver killing thread when taking screenshot. Game crashes

Hello,

We recently saw a case where our app crashed while taking multiple screenshots from the meta quest menu.
The error in logs was

Abort message: 'DeadlockObserver killing locked thread! [clientThreadMutex_UpdateInputData_PostLock]'

backtrace:
      #00 pc 00000000000cf138  /apex/com.android.runtime/lib64/bionic/libc.so (__ioctl+8) (BuildId: d8622d5c4e8dd5e689e617ac5ed845ff)
      #01 pc 00000000000933c8  /apex/com.android.runtime/lib64/bionic/libc.so (ioctl+152) (BuildId: d8622d5c4e8dd5e689e617ac5ed845ff)
      #02 pc 0000000000046894  /system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+256) (BuildId: 314b133a4efbd6190f40cc18ebf94921)
      #03 pc 00000000000478ac  /system/lib64/libbinder.so (android::IPCThreadState::waitForResponse(android::Parcel*, int*)+60) (BuildId: 314b133a4efbd6190f40cc18ebf94921)
      #04 pc 00000000000475fc  /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+216) (BuildId: 314b133a4efbd6190f40cc18ebf94921)
      #05 pc 0000000000040448  /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+192) (BuildId: 314b133a4efbd6190f40cc18ebf94921)
      #06 pc 00000000000de388  /system/lib64/libandroid_runtime.so (android_os_BinderProxy_transact(_JNIEnv*, _jobject*, int, _jobject*, _jobject*, int)+152) (BuildId: dd10efdb7a2da97a24f23fa08d0fcde2)

 We are unsure if there are steps we can take to resolve this issue.

Would an error like this have been caused by some part of our app not responding correctly to the take a picture command, or is this error in the runtime and beyond our control?