MR_performFetch deadlock #140

Closed
ekurutepe opened this Issue Feb 10, 2012 · 5 comments

Comments

Projects
None yet
6 participants
@ekurutepe

Created two NSFetchedResultsControllers with the same entity in two different view controllers in a UITabbarController. The first view works great but when switching to the second view controller causes a deadlock in MR_performFetch in Private Queue mode (iOS 5). Thread Isolation mode (iOS 4.3) works fine.

Is it me doing something wrong?

@fossli

This comment has been minimized.

Show comment Hide comment
@fossli

fossli Feb 13, 2012

I also experience this. Using thread isolation works fine.

fossli commented Feb 13, 2012

I also experience this. Using thread isolation works fine.

@mmittelman

This comment has been minimized.

Show comment Hide comment
@mmittelman

mmittelman Mar 2, 2012

I forced switching to thread isolation by changing this constant:
kCFCoreFoundationVersionNumber_iPhoneOS_5_0 1000.0

now I have no problems with deadlocks.

I forced switching to thread isolation by changing this constant:
kCFCoreFoundationVersionNumber_iPhoneOS_5_0 1000.0

now I have no problems with deadlocks.

@sghael

This comment has been minimized.

Show comment Hide comment
@sghael

sghael Mar 2, 2012

We had the same problem. forked and ripped out the deadlocking code, which simplified a lot of code and obviates the need to set the magical kCFCoreFoundationVersionNumber_iPhoneOS_5_0 const.

https://github.com/sghael/MagicalRecord

sghael commented Mar 2, 2012

We had the same problem. forked and ripped out the deadlocking code, which simplified a lot of code and obviates the need to set the magical kCFCoreFoundationVersionNumber_iPhoneOS_5_0 const.

https://github.com/sghael/MagicalRecord

@dukeflyheli

This comment has been minimized.

Show comment Hide comment
@dukeflyheli

dukeflyheli Mar 22, 2012

I also experience major threading locks because of the private queue mode is not correctly implemented. Forcing thread isolation seems to work fine at this time.

I also experience major threading locks because of the private queue mode is not correctly implemented. Forcing thread isolation seems to work fine at this time.

@blackgold9

This comment has been minimized.

Show comment Hide comment
@blackgold9

blackgold9 Sep 23, 2012

Contributor

This is a known issue with ios 5. iOS 6 resolves this.

Contributor

blackgold9 commented Sep 23, 2012

This is a known issue with ios 5. iOS 6 resolves this.

@blackgold9 blackgold9 closed this Sep 23, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment