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 6653109
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T01:13:37+00:00 2026-05-26T01:13:37+00:00

I have an iPhone app that freezes sometimes when saving CoreData and then doesn’t

  • 0

I have an iPhone app that freezes sometimes when saving CoreData and then doesn’t relaunch. I did have a second thread that uses the database, but I think I have followed the pattern to make a separate context for that thread. Here is the crash report from the relaunch. Any ideas?

I have tried changing it to only run with one thread and here is the latest freeze point after entering the background.

#0  0x30851b98 in fsync
#1  0x3094e694 in _sqlite3_purgeEligiblePagerCacheMemory
#2  0x3094e6b8 in _sqlite3_purgeEligiblePagerCacheMemory
#3  0x30945372 in sqlite3_compileoption_get
#4  0x30957f06 in sqlite3_extended_errcode
#5  0x3095dc20 in sqlite3_extended_errcode
#6  0x3095dd8e in sqlite3_extended_errcode
#7  0x309646f8 in sqlite3_clear_bindings
#8  0x3098845a in sqlite3_open16
#9  0x3094495a in sqlite3_step
#10 0x31a1dc20 in _execute
#11 0x31acc6e8 in -[NSSQLiteConnection commitTransaction]
#12 0x31aca646 in -[NSSQLiteConnection endPrimaryKeyGeneration]
#13 0x31abeab4 in -[NSSQLCore prepareForSave:]
#14 0x31a4acd0 in -[NSSQLCore saveChanges:]
#15 0x31a1591e in -[NSSQLCore executeRequest:withContext:error:]
#16 0x31a1538a in -[NSPersistentStoreCoordinator executeRequest:withContext:error:]
#17 0x31a48544 in -[NSManagedObjectContext save:]
#18 0x000080aa in -[KPersistence saveManagedObjects:] at KPersistence.m:242
#19 0x00004320 in -[KinKastAppDelegate applicationDidEnterBackground:] at KinKastAppDelegate.m:126

Here is my implementation of saveManagedObjects

-(BOOL)saveManagedObjects:(NSError **)error
{
    [persistentStoreCoordinator lock];
    BOOL success = YES;
    if (managedObjectContext != nil) {
        if ([managedObjectContext hasChanges] && ![managedObjectContext save:error]) {
            VLog(@"Unresolved error %@, %@", *error, [*error userInfo]);
            success = NO;
        } 
    }
    [persistentStoreCoordinator unlock];
    return success;
}
  • 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-26T01:13:37+00:00Added an answer on May 26, 2026 at 1:13 am

    So I now believe the problem was that I was sometimes writing an NSNumber with float value to an integer field. This caused the copy in memory to be different than the copy read from the database, and this caused the infinite merge loop. But if you restarted the app it worked fine because the value was simply an integer from then on.

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

Sidebar

Related Questions

i have an iphone app that uses coredata to store its contents. users often
I have an iphone app that converts a image into NSData & then converts
I have an iPhone app that hides the status bar. However, my main view
I have an iPhone app that compiles and runs fine in the Simulator on
I have an iPhone app that heavily relies on the OpenCV library; as such,
I have an iPhone app that is based on a navigation controller. I have
I have an iphone app that I built based off a tutorial (for a
I have an iPhone app that shows a simple view (View 1) that has
I have an iPhone app that uses the json-framework . I moved some of
I have a simple iphone app that's based on the CrashLanding sample app. So

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.