Reputation: 45
This is a very weird error I'm getting but that wasn't happening literally last night and I haven't changed anything in the project since then.
I read questions about the same problem but it seems like no one can figure it out, it could be the fact that the app takes too long to start apparently which makes it crash but I don't know.
I've deactivated Enable Startup Tracing
and Use the concurrent garbage collector
in the android settings as well as made sure the x86_x64
arch support was checked in the advanced android settings like I saw online but no success so far.
Here's the output when it crashes:
[not.poppinornot] Attempt to remove non-JNI local reference
[monodroid-debug] Trying to initialize the debugger with options: --debugger-agent=transport=dt_socket,loglevel=0,address=10.0.2.2:22883,embedding=1
[mono] debugger-agent: Unable to connect to 10.0.2.2:22883
[not.poppinornot] mutex.cc:432] destroying mutex with owner or contenders. Owner:10086
[not.poppinornot] art/dt_fd_forward/dt_fd_forward.cc:323 - Failed to receive fds!: Success
[libc] FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x7e2dfcfdb1f8)
[libc] Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 10081 (not.poppinornot), pid 10081 (not.poppinornot)
The output since I unchecked Use the concurrent garbage collector
is the same but just stops at either [mono] debugger-agent: Unable to connect to 10.0.2.2:22883
or [not.poppinornot] mutex.cc:432] destroying mutex with owner or contenders. Owner:10086
Edit: the app is being compiled using Android Version 11.0, and the simulators I'm using are using Android 15.0 & API 35, if that helps.
Also, tried with a new simulator and it works this time, I don't know what's the difference between the two besides the fact that one is the Pixel 6 Pro and the other one the Pixel 7, but the 6 says + Google APIs
under it and the 7 says + Google Play
under it.
Upvotes: 0
Views: 26