Fatal signal 11 (SIGSEGV) in 0.9.9

[arnis71]

I am getting this error when I am trying to save the object.
03-15 00:35:34.293 27981-27981/com.rbot.mdd.tester A/libc: Fatal signal 11 (SIGSEGV) at 0x605c500a (code=1), thread 27981 (rbot.mdd.tester)

There is no such issue in ObjectBox version 0.9.8 and 0.9.9-snapshot. Any ideas why is this happening? I will provide more information as soon as get the exact place where this error is being thrown.

[arnis71]

I traced the error to method put(T entity) in class Box.class. And the line that throws the exception is this.commitWriter(cursor);.

[arnis71]

UPDATE
I figured out that this problem occurs whenever I try to save the object inside Accessibility Service when I navigate in phone launcher. So far the issue is reproducible with Lenovo launcher and LG launcher, touchwiz works fine.

nativeDestroy(this.cursor); in Cursor.class seems to be the method that throws the exception.

[FabianTerhorst]

You tried wrapping around an async transaction? store.runInTxAsync()

[arnis71]

That works! Thank you, it saved me :)

But is it a workaround or this is a right way to put the objects?

[FabianTerhorst]

Its faster when you have multiple put calls.

[greenrobot]

It would be super awesome to have a reproducible test case triggering the sigsegv.

[greenrobot]

Cannot do anything without additional info. Don't hesitate to reopen if you gather more info.