Closed ghost closed 9 years ago
@christianlanz I'm guessing that self
here has some reference to an Object
that was obtained on another thread. This is a duplicate of https://github.com/realm/realm-cocoa/issues/1893, and we intend to make it safe to deallocate an Object
on any thread in an upcoming release of Realm.
I just updated from Realm v0.92.2 to v0.92.3 and now our app keeps crashing if we execute the following code in our sync logic:
Reason: Realm accessed from incorrect thread
I always instantiate and access the Realm object in the same thread (no shared realm between threads). Don't know what you changed vom v0.92.2 to v0.92.3 but that wasn't a good idea ^^