Fatal signal 6 (SIGABRT), code -6 (SI_TKILL)

[Kolyall]

How frequently does the bug occur?

All the time

Description

realmVersion : '10.10.1'

After some operation, the database breaks and the application does not start anymore. At the next starts of the application, the crash repeats.

Stacktrace & log output

2022-06-20 11:31:41.673 4699-4771/? A/libc: Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 4771 (REALM_SCHEDULER), pid 4699 (com.play.dev)
2022-06-20 11:31:41.800 4865-4865/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2022-06-20 11:31:41.800 4865-4865/? A/DEBUG: Build fingerprint: 'HUAWEI/ANE-LX1/HWANE:9/HUAWEIANE-L21/9.1.0.352C461:user/release-keys'
2022-06-20 11:31:41.800 4865-4865/? A/DEBUG: Revision: '0'
2022-06-20 11:31:41.800 4865-4865/? A/DEBUG: ABI: 'arm64'
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG: Happend: 'Mon Jun 20 11:31:41 2022
    '
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG: SYSVMTYPE: Art
    APPVMTYPE: Art
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG: pid: 4699, tid: 4771, name: REALM_SCHEDULER  >>> com.play.dev <<<
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG: Abort message: 'terminating with uncaught exception of type realm::util::DecryptionFailed: Decryption failed
    Exception backtrace:
    <backtrace not supported on this platform>'
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG:     x0  0000000000000000  x1  00000000000012a3  x2  0000000000000006  x3  0000000000000008
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG:     x4  fefefefefefeff50  x5  fefefefefefeff50  x6  fefefefefefeff50  x7  7f7f7f7f7f7f7f7f
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG:     x8  0000000000000083  x9  06ed1a4e65dca826  x10 0000000000000000  x11 fffffffc7ffffbdf
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG:     x12 0000000000000001  x13 0000000062b0306d  x14 0009d5b33be27161  x15 000030608ab535a1
2022-06-20 11:31:41.801 4865-4865/? A/DEBUG:     x16 00000073098712c0  x17 00000073097b033c  x18 0000000000000001  x19 000000000000125b
2022-06-20 11:31:41.802 4865-4865/? A/DEBUG:     x20 00000000000012a3  x21 000000726586c898  x22 ffffff80ffffffc8  x23 000000726586c950
2022-06-20 11:31:41.802 4865-4865/? A/DEBUG:     x24 000000726586c830  x25 000000726586c870  x26 0000007262539000  x27 0000007266621000
2022-06-20 11:31:41.802 4865-4865/? A/DEBUG:     x28 0000007266621000  x29 000000726586c7a0
2022-06-20 11:31:41.802 4865-4865/? A/DEBUG:     sp  000000726586c760  lr  00000073097a4e68  pc  00000073097a4e90
2022-06-20 11:31:41.804 4865-4865/? A/DEBUG: backtrace:
2022-06-20 11:31:41.804 4865-4865/? A/DEBUG:     #00 pc 0000000000022e90  /system/lib64/libc.so (abort+116)
2022-06-20 11:31:41.804 4865-4865/? A/DEBUG:     #01 pc 000000000034d1a8  /data/app/com.play.dev-gsTu5vKHEkNxoICHhqRPkQ==/base.apk (offset 0x1bae000)

Can you reproduce the bug?

Yes, sometimes

Reproduction Steps

No response

Version

10.10.1

What SDK flavour are you using?

Local Database only

Are you using encryption?

Yes, using encryption

Platform OS and version(s)

Android, API 31, Emulator Nexus 5X

Build environment

Android Studio version: 2021.2.1 Patch 1 Android Build Tools version: ... Gradle version: classpath 'com.android.tools.build:gradle:7.2.1'

[Kolyall]

Also on HUAWEIANE-L21

[mattylase]

Seconding this issue strongly - we are experiencing a huge amount of issues from Realm in the native layer.

This is using the Realm Gradle Plugin 10.11.0.

[ittna]

Same here. I remember getting decryption failed error on emulator with older realm versions also but not on real device. Now it happens on real devices too.

[thuannv]

I also experienced same issue, random crashes and repeatedly after I kill app and reopen it. I've been searching around for resolution but no helps out there.

2022-07-01 16:36:41.934 2492-2492/? I/crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
2022-07-01 16:36:41.934 730-730/? I//system/bin/tombstoned: received crash request for pid 2392
2022-07-01 16:36:41.935 2492-2492/? I/crash_dump64: performing dump of process 2194 (target tid = 2392)
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG: Build fingerprint: 'HUAWEI/SPN/HWSPN:9/HUAWEISPN/SPN-LGRP2-OVS 9.1.1.180(log):user/release-keys'
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG: Revision: '0'
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG: ABI: 'arm64'
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG: Happend: 'Fri Jul  1 16:36:41 2022
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG: pid: 2194, tid: 2392, name: mqt_js  >>> com.mservice.momotransfer <<<
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x0  0000000000000000  x1  0000000000000958  x2  0000000000000006  x3  0000000000000008
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x4  fefeff00df9c9b0a  x5  fefeff00df9c9b0a  x6  fefeff00df9c9b0a  x7  7f7f7f7fffffff7f
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x8  0000000000000083  x9  5cb3ac60d238c282  x10 0000000000000000  x11 fffffffc7ffffbdf
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x12 0000000000000001  x13 0000000000000000  x14 ffffffffffffffff  x15 00000000ebad607f
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x16 0000007a434f02c0  x17 0000007a4342ee34  x18 00000000ebad6082  x19 0000000000000892
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x20 0000000000000958  x21 0000000000000001  x22 000000799c48a700  x23 0000007998cf9588
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x24 0000000000000000  x25 000000799d04d188  x26 0000000000000000  x27 0000000000000000
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     x28 000000799d04d160  x29 0000007998cf3650
2022-07-01 16:36:41.942 2492-2492/? A/DEBUG:     sp  0000007998cf3610  lr  0000007a43423960  pc  0000007a43423988

[edualonso]

Hi @Kolyall. The trace you provide us is incomplete. Could you paste the entire stacktrace of the native crash? It is necessary for us to have access to the full stracktrace to be able to unroll it and understand what is causing the crash in Core. The stacktrace needs to be in the following https://developer.android.com/ndk/guides/ndk-stack.

[edualonso]

@thuannv the stacktrace you provided is incomplete so we cannot determine whether it is the same type of crash as the one reported in this issue. In any case, I would recommend you create a new issue with the full stacktrace so that we don't get lost in between problems under the same thread.

[rorbech]

We addressed some corruption bugs related to encryption in 10.11.0. If you keep seeing this after upgrading could then please try to supply the full stack trace as mentioned above.

[clementetb]

Closing due to inactivity.