Native crash at /data/app-lib/com.gmspartnersltd.earthmiles-1/librealm-jni.so

[shahzaibmuneeb]

Any idea on what could be causing this?

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'motorola/XT926_verizon/vanquish:4.4.2/KDA20.62-15.1/15:user/release-keys'
Revision: 'p300'
pid: 15508, tid: 15508, name: sltd.earthmiles  >>> com.gmspartnersltd.earthmiles <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000004
    r0 608a8ec0  r1 00000001  r2 608a78d8  r3 00000000
    r4 608a8ec0  r5 60a86008  r6 00000004  r7 00000001
    r8 608a8ec0  r9 00000c20  sl bed5a278  fp 60887a18
    ip 00000001  sp bed5a180  lr 60a3b491  pc 60a31006  cpsr 400e0030
    d0  0000000000000000  d1  0000000000000000
    d2  0000000000000000  d3  0000000000000000
    d4  577126c0579823b0  d5  579d9268579d9230
    d6  577127a057712768  d7  57712810579d92a0
    d8  0000000000000000  d9  0000000000000000
    d10 0000000000000000  d11 0000000000000000
    d12 0000000000000000  d13 0000000000000000
    d14 0000000000000000  d15 0000000000000000
    d16 416c70e000000002  d17 0000000200000002
    d18 00000004416c70e0  d19 0000000200000003
    d20 00000000416c61e8  d21 0000000000000000
    d22 416c6890421df2e8  d23 0000000000000000
    d24 4240ec9cc1238000  d25 0003000000030000
    d26 0000002e0000002d  d27 000000300000002f
    d28 0100010001000100  d29 0100010001000100
    d30 0000000000000000  d31 0000000000000000
    scr 20000010

backtrace:
    #00  pc 0007d006  /data/app-lib/com.gmspartnersltd.earthmiles-1/librealm-jni.so
    #01  pc 0008748d  /data/app-lib/com.gmspartnersltd.earthmiles-1/librealm-jni.so

code around pc:
    60a30fe4 46022300 f0024630 e7eefeb3 6089f504  
    60a30ff4 f7ea4629 4620fd57 f7ff2100 f8d4fc8f  
    60a31004 f8533448 e8bd0027 e92d87f0 460541f0  
    60a31014 8234f8d0 4617460e 45442400 4621d00a  
    60a31024 f7ff4628 4631ffbb 3401463a 6cdb6803  
    60a31034 e7f24798 81f0e8bd 41f3e92d 46074616  
    60a31044 0042e88d e893466a 461c0003 fc3cf7f7  
    60a31054 42986823 d0094605 2c08f850 429a9b00  
    60a31064 f850d104 9b012c04 d00e429a 46316938  
    60a31074 ffa3f7bf 4629b948 4620466a fe80f7d8  
    60a31084 46316938 f7ff4622 b002ffc0 81f0e8bd  
    60a31094 43f8e92d 69004605 4691460e fa51f7c7  
    60a310a4 240068f7 42bc4680 4621d00b f7d54630  
    60a310b4 4641f8fd 3401464b 46284602 ffbcf7ff  
    60a310c4 e8bde7f1 e92d83f8 460641f0 46174688  
    60a310d4 fb3ef7bf 0301ea50 f110d016 464234ff  

code around lr:
    60a3b470 46206823 3b012101 e8bd6023 f7b741f0  
    60a3b480 e92dbdf7 461741f3 4680461c fd88f7f5  
    60a3b490 ac014621 46384606 fd82f7f5 46054639  
    60a3b4a0 f7c94620 4621fd54 0010f106 f975f7f3  
    60a3b4b0 f7f14620 4620ffda 61754641 fd47f7c9  
    60a3b4c0 f1054621 f7f30014 4620f968 ffcdf7f1  
    60a3b4d0 b00261ae 81f0e8bd 4615b5f0 e000f8d0  
    60a3b4e0 6846460f cd0fb087 c40f466c e8954632  
    60a3b4f0 466b0003 0003e884 46394670 fe4cf7fd  
    60a3b500 bdf0b007 41f0e92d 8b02ed2d 8b40eeb0  
    60a3b510 4604b084 2101460f f7b74616 4639fda9  
    60a3b520 f7f54620 4631fd3d 0b48eeb0 f940f7ce  
    60a3b530 689d6ae3 f105b315 46210804 4640ac04  
    60a3b540 fe98f7ec 4640211f fe31f7ec f8441c43  
    60a3b550 23083d0c 70034621 f7bc4638 4630fe02  
    60a3b560 f7bc4621 ab04fdfe ed239a01 cb038b02

[beeender]

#2089 has been reported with similar back trace, but we haven't be able to reproduce it.
#1945 might solve this crash.

What is the Realm version you are using? And how many crashes you have seen?

[shahzaibmuneeb]

0.80.1 and that was the first of that crash, I am now upgrading to 0.87.4. That should resolve the issue, right?

[beeender]

@shahzaibmuneeb I hope it is a know issue that we have fixed. But without enough information, it is really hard for us to confirm that.

Updating to the 0.87.4 won't be harmful and probably fixed the problem. Please let us know if the new version helps.

[shahzaibmuneeb]

Have upgraded, will report back on conclusion - thanks.

[kneth]

@shahzaibmuneeb How did the upgrade go?

[shahzaibmuneeb]

It seems to have been resolved, I could never reproduce the error in the first place so it's hard to say but the crash hasn't happened since for any of our users.

[kneth]

@shahzaibmuneeb I'll close the issue. If you experience the issue again, don't hesitate to either reopen or create a new issue.