Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7368291
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T03:38:55+00:00 2026-05-29T03:38:55+00:00

I am trying to create some methods that should make it easier to perform

  • 0

I am trying to create some methods that should make it easier to perform Core Data stuff in the background. What I’m doing is:

  • Use NSOperationQueue‘s -addOperationWithBlock: to create a background thread
  • In the background thread, create an NSManagedObjectContext with the same persistentStoreCoordinator as the context on the main thread and with undoManager set to nil
  • Add an observer to the default notification center to listen for NSManagedObjectContextDidSaveNotification notifications and handle them like this:

    - (void)mergeChanges:(NSNotification *)notification
    {
        dispatch_sync(dispatch_get_main_queue(), ^{
            [_mainContext mergeChangesFromContextDidSaveNotification:notification];
        });
    }
    
  • Execute a block that was passed in and that does all the Core Data stuff. Periodically, it calls save: on the background context

  • Once everything is done, remove the observer from the notification center

The described method can be found below.

Everything works as expected. I can pass in blocks that add data, update data or remove data. But: I get the following error when I close the app with some data, re-open it and then try to delete data in the background:

CoreData: error: Serious application error. An exception was caught
from the delegate of NSFetchedResultsController during a call to
-controllerDidChangeContent:. CoreData could not fulfill a fault for […]

As apparent from the error, I am using an NSFetchedResultsController to display data. The cache of the controller is set to nil.

Any suggestions on how to fix this?


Here is the relevant code. Note that I’m using ARC.

FJCoreDataBackgroundBlock is defined like so:

typedef void(^FJCoreDataBackgroundBlock)(NSManagedObjectContext *backgroundContext);

The method to perform a bunch of Core Data stuff in the background

- (void)performBlockInBackground:(FJCoreDataBackgroundBlock)block
{
    [FJSharedOperationQueue addOperationWithBlock:^{

        self.managedObjectContext = [[NSManagedObjectContext alloc] init];
        [_managedObjectContext setUndoManager:nil];
        [_managedObjectContext setPersistentStoreCoordinator:self.persistentStoreCoordinator];

        [self setupNotificationCenterObserverForContext:_managedObjectContext];

        FJCoreDataBackgroundBlock backgroundBlock = [block copy];
        backgroundBlock(self.managedObjectContext);

        [self saveBackgroundContext];
        [self saveMainContext];
        [self removeNotificationCenterObserver];
    }];
}

The implementation of FJSharedOperationQueue:

+ (NSOperationQueue *)sharedQueue
{
    static dispatch_once_t predicate = 0;

    __strong static NSOperationQueue *_sharedQueue = nil;

    dispatch_once(&predicate, ^{
        _sharedQueue = [[NSOperationQueue alloc] init];
        [_sharedQueue setMaxConcurrentOperationCount:1];
    });

    return _sharedQueue;
}

+ (void)addOperationWithBlock:(void (^)(void))block
{
    [[FJSharedOperationQueue sharedQueue] addOperationWithBlock:block];
}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T03:38:56+00:00Added an answer on May 29, 2026 at 3:38 am

    Now that is weird: I was shuffling around code lines in the block that deletes objects. Before it looked like this:

    FJCoreDataHelper *helper = [[FJCoreDataHelper alloc] initUsingMainManagedObjectContext:[self mainContext]];
    
    [helper performBlockInBackground:^(NSManagedObjectContext *backgroundContext) {
    
        // [Fetch objets here...]
    
        // Delete:
    
        const int kSaveThreshold = 50;
        for (int card = 0, count = [allCards count]; card < count; card++)
        {
            [backgroundContext deleteObject:[allCards objectAtIndex:card]];
    
            if (card % kSaveThreshold == 0)
            {
                [helper saveBackgroundContext];
            }
        }
        }];
    

    To fix it, I simply had to save the main context after saving the background context:

    [helper performBlockInBackground:^(NSManagedObjectContext *backgroundContext) {
    
        // [Fetch objets here...]
    
        // Delete:
    
        const int kSaveThreshold = 50;
        for (int card = 0, count = [allCards count]; card < count; card++)
        {
            [backgroundContext deleteObject:[allCards objectAtIndex:card]];
    
            if (card % kSaveThreshold == 0)
            {
                [helper saveBackgroundContext];
                [helper saveMainContext];
            }
        }
        }];
    

    If I save only the background context, it crashes. If I save the main context first, it also crashes. I find this weird because I thought that merging the background context into the main context would also save the main context…

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am trying to create some charts of data (eg http://www.amibroker.com/ ). Is there
I am trying to create some dynamic html out of some data from db.
I am trying to use the googlecharts gem to create some quick charts. Here
I'm trying to create some HtmlHelper extensions and ran into a bit of a
I am trying to create some reusable components in Silverlight2 . The difficulty comes
I am trying to create some rules and facts on a certain situation. The
I am trying to create some global variables in a firefox extension. In my
I am trying to create some script variables in T-SQL as follows: /* Deployment
I'm trying to implement the WMD editor used on StackOverflow to create some basic
I'm trying to be a good developer and create some documentation before I start

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.