-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
native crash while deleting obj from realm. #1983
Labels
Comments
Hi @RobertBorg |
dalinaum
added a commit
that referenced
this issue
May 11, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 11, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 11, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 11, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 11, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 11, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 12, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 13, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 13, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 13, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 13, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 13, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 14, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 17, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 17, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 17, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 18, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 19, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
dalinaum
added a commit
that referenced
this issue
May 19, 2016
1. Fix async transaction problelm when async query already exist. 2. Add the warning when closing a Realm with pending transactions. Fix #1983
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Possible duplicate of #1982
While committing an transaction that deletes an Obj1 from realm i get a native crash.
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x288 in tid 26921 (app)
I'm using 'io.realm:realm-android:0.87.0' from "http://dl.bintray.com/realm/maven"
while deleting the obj1 there is an active subscription to a subquery of obj1. Something like this:
guithread;
obj1.getObj2List().where().equalTo("someField", "asd").findAll().asObservable().subscribe(/code that only calls size on RealmResults/)
later in other thread:
r.beginTransaction();
obj1.getObj2List().where().equalTo("someField", "asd").findAll().clear();
r.commitTransaction();
if(obj1.getObj2List().size() == 0) {
r.beginTransaction();
obj1.removeFromRealm();
r.commitTransaction(); // crash
}
not subscribing in guithread prevents the problem from happening
I'm using Android Studio 2.0 built on nov 21 and i think i'm on latest LTS release of ubuntu
If this is not enough to pinpoint the problem i'll probably be able to create isolated example.
The text was updated successfully, but these errors were encountered: