objectbox-java: Crash: Java_io_objectbox_query_Query_nativeFind

Issue Basics

  • ObjectBox version (are using the latest version?): 1.5.0
  • Reproducibility: Not always

I received the following crash when I called box.find method. This only happened sometimes. But once it happened, it would always happen later. Any clue ?

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/starltexx/starlte:8.0.0/R16NW/G960FXXU1BRE6:user/release-keys'
Revision: '26'
ABI: 'arm'
pid: 763, tid: 916, name: MyHandlerThread  >>> com.something <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x83804403
    r0 83804403  r1 00000036  r2 b7c957ac  r3 c1be0c93
    r4 b7c957ac  r5 bada9e78  r6 b7b57534  r7 bbdfd468
    r8 bc0a5488  r9 bc0a5480  sl 000003e8  fp bc0a5480
    ip e5826d5c  sp bbdfd458  lr c1bd7437  pc c1be0cb0  cpsr a0070030
backtrace:
    #00 pc 00051cb0  /data/app/com.something-v37ezjtrI-iGSmyORUO3eQ==/lib/arm/libobjectbox.so
    #01 pc 00048435  /data/app/com.something-v37ezjtrI-iGSmyORUO3eQ==/lib/arm/libobjectbox.so
    #02 pc 0004acd9  /data/app/com.something-v37ezjtrI-iGSmyORUO3eQ==/lib/arm/libobjectbox.so
    #03 pc 0004aea7  /data/app/com.something-v37ezjtrI-iGSmyORUO3eQ==/lib/arm/libobjectbox.so
    #04 pc 00047feb  /data/app/com.something-v37ezjtrI-iGSmyORUO3eQ==/lib/arm/libobjectbox.so
    #05 pc 0007d33d  /data/app/com.something-v37ezjtrI-iGSmyORUO3eQ==/lib/arm/libobjectbox.so (Java_io_objectbox_query_Query_nativeFind+72)
    #06 pc 000fa21d  /data/app/com.something-v37ezjtrI-iGSmyORUO3eQ==/oat/arm/base.odex (offset 0x38000)

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 35 (16 by maintainers)

Most upvoted comments

@LeeKingHung You have to check the device.

The just released version 2.3.0 should fix this. Please verify and let us know. Thank you!

No worries. I used findIds() instead and now there is no crash observed.

By the way I noticed something, not sure it is related to this issue or not: I ran the original query in one thread, and then ran another query (same box but differerent query) in another thread ( both queries were read query and were wrapped in BoxStore.runInReadTx() ), the crash would always happen.

I have emailed you for that. Thanks.

So far I only encountered this issue once with 2.0.0-beta (not 2). I will use beta2 and continue to observe.