Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fatal signal 11 (SIGSEGV) in 0.9.9

See original GitHub issue

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.

Issue Analytics

State:
Created 7 years ago
Comments:7 (2 by maintainers)

Top GitHub Comments

2reactions

FabianTerhorstcommented, Mar 16, 2017

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

0reactions

greenrobotcommented, Apr 11, 2017

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

Top Results From Across the Web

Android Fatal signal 11 (SIGSEGV) at 0x636f7d89 (code=1 ...

Your application is accessing memory outside of its address space. This is most likely an invalid pointer access. SIGSEGV = segmentation fault in...

Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 2327

This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application.

SIGSEGV: Linux Segmentation Fault | Signal 11, Exit code 139

It indicates an attempt by a program to write or read outside its allocated memory—either because of a programming error, a software or...

Bug listing with status RESOLVED with resolution FIXED as at ...

Bug listing with status RESOLVED with resolution FIXED as at 2022/12/11 06:46:03 ... Bug:1313 - "mozilla-0.9.9-r1 ebuild died on me w/ Gentoo 1.0" ......

Why does Splunk Enterprise 7.1.2 crashes sporadica...

Received fatal signal 11 (Segmentation fault). Cause: No memory mapped at address [0x0000000000000010]. Crashing thread: TcpChannelThread