realm/realm-java

[realm-core-13.23.0] Assertion failed: false

sathishwebdev opened this issue · 4 comments

sathishwebdev commented

SDK and version

SDK : java-android
Version: 13.23.0

Observations

  • How frequent do the crash occur?
    this is the first time this crash occured
  • Does it happen in production or during dev/test?
    dev
  • Can the crash be reproduced by you?
    no

Crash log / stacktrace

E /tmp/realm-java/realm/realm-library/src/main/cpp/jni_util/jni_utils.cpp:54: [realm-core-13.23.0] Assertion failed: false

!!! IMPORTANT: Please report this at https://github.com/realm/realm-core/issues/new/choose
2024-06-05 20:00:56.777 2501-2501 libc A FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x74cc1f1b50)
---------------------------- PROCESS STARTED (6491) for package ----------------------------
2024-06-05 20:00:56.778 2501-6489 libc A Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 6489 (Studio:Socket), pid 2501 (duct.illuminate)
2024-06-05 20:00:57.052 2501-3852 libc A FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x75d8eee9a0)
2024-06-05 20:00:57.052 2501-3853 libc A FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x75d8eee9a0)
2024-06-05 20:00:57.099 6492-6492 DEBUG pid-6492 A pid: 2501, tid: 6489, name: Studio:Socket >>> <<<
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#1 pc 00000000007a8744 /data/app/-UtPfIj9EHkWwVNtR91aX6w==/base.apk!librealm-jni.so (offset 0x11439000) (BuildId: 34c2baa0e05e15474c7de859b65b28cb4506f3da)
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#2 pc 00000000007a8aa0 /data/app/-UtPfIj9EHkWwVNtR91aX6w==/base.apk!librealm-jni.so (offset 0x11439000) (BuildId: 34c2baa0e05e15474c7de859b65b28cb4506f3da)
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#3 pc 00000000007a88d8 /data/app/-UtPfIj9EHkWwVNtR91aX6w==/base.apk!librealm-jni.so (offset 0x11439000) (BuildId: 34c2baa0e05e15474c7de859b65b28cb4506f3da)
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#4 pc 00000000007a8754 /data/app/-UtPfIj9EHkWwVNtR91aX6w==/base.apk!librealm-jni.so (offset 0x11439000) (BuildId: 34c2baa0e05e15474c7de859b65b28cb4506f3da)
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#5 pc 00000000004e7550 /data/app/c-UtPfIj9EHkWwVNtR91aX6w==/base.apk!librealm-jni.so (offset 0x11439000) (BuildId: 34c2baa0e05e15474c7de859b65b28cb4506f3da)
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#8 pc 000000000013b024 /data/data/ccode_cache/libjvmtiagent_arm64.so
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#9 pc 00000000001287e4 /data/data//code_cache/libjvmtiagent_arm64.so
2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A realm/realm-core#10 pc 000000000012e56c /data/data/c/code_cache/libjvmtiagent_arm64.so

sync-by-unito commented

➤ PM Bot commented:

Jira ticket: RCORE-2154

nicola-cab commented

Hello, this does not look like a core issue, but a problem in the bridge code between core and JNI. @clementetb @rorbech. It looks like the mutex got deallocated when the code tried to lock it.
pthread_mutex_lock called on a destroyed mutex

sync-by-unito commented

➤ PM Bot commented:

Jira ticket: RJAVA-1265