title: What are NSManagedObjectContext best practices?
body: <p>I'm working with a Navigation Controller based iOS app. There are multiple tableView screens that pull and save data from a Core Data persistent store. Most of the data for the different table views comes from NSFetchedResultsController instances or NSFetchRequests.</p>
  
  <p>The app works as intended but I have been getting a few random crashes and glitches that seem to be related to Core Data. For example sometimes when I save the context the app will crash but not always. Another thing I've been seeing is the very first tableView doesn't always update the reflect the data that was modified in it's detail view.</p>
  
  <p>Currently I'm passing around a single Managed Object Context that was created in the app delegate to each of the different view controllers by setting the context property of the view controller just before I push it onto the navigation stack.</p>
  
  <p>This seems like a clunky, hacky way of getting the job done. Is there a better design pattern to use?</p>
  
  <p>I noticed in one of the WWDC sessions using delegation but I've never used creating my own delegates before and haven't been able to puzzle it out of the WWDC session.</p>
  
  <p>Thanks. </p>
  
  <p>=)</p>