Uploaded image for project: 'Realm Core'
  1. Realm Core
  2. RCORE-2154

[realm-core-13.23.0] Assertion failed: false

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None

      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
      <backtrace not supported on this platform>
      !!! 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 #01 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 #02 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 #03 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 #04 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 #05 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 #08 pc 000000000013b024 /data/data/ccode_cache/libjvmtiagent_arm64.so
      2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A #09 pc 00000000001287e4 /data/data//code_cache/libjvmtiagent_arm64.so
      2024-06-05 20:00:57.116 6492-6492 DEBUG pid-6492 A #10 pc 000000000012e56c /data/data/c/code_cache/libjvmtiagent_arm64.so

            Assignee:
            Unassigned Unassigned
            Reporter:
            unitosyncbot Unito Sync Bot
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: