_PFObjectIDFastHash64 Crash EXC_BAD_ACCESS KERN_INVALID_ADDRESS

I am also having this issue. Compiling in xCode 11.7 fixes the issue - but obviously that is not a good long-term solution. Does anyone know if xCode 12.5 fixes this (and iOS 14.5) ?. I have not tried it yet, but its kind of random and hard to replicate on-demand.

We are seeing this in a newly released app, built using Xcode 12.5 (12E262).

So I am running xCode 12.4 on iOS 14.5 and I can replicate this on demand. In our app we use afnetworking to get a load of data and save it to core data. If I do a force quit while this "sync" is going on (asynchronous) and then go back into the app and then let it "resync" the data it eventually crashes. Not always at the same point.

As to why? I have no idea what-so-ever - but at least I can replicate it on demand.

The only fix I have right now is to use xCode 11.7 to build the app. I cannot crash it.

I have tried in 12.5 but not yet replicated the issue - but per the prior post it seems it is there too.

so I can now replicate in 12.5 running on 14.5 ios. Here is what i know so far:

I can replicate it if I force quit my app while it is syncing data into core data. then if I go back in quickly it crashes. If I leave it a while (between the force quit - or I go back in again after the crash) then it does not crash. It is as though that there is something left over from the force quit that it does not like when I go in and sync data into core data again.

super annoying and very puzzling.

having the same crash on Crashlytics ,Any solution on this yet?

I am pushed latest build via xcode12.4, after that my app crashed randomly and some time frequently .

Have any solution, kindly let me know.

Thanks

Logs:

Thread 3 name: Dispatch queue: NSManagedObjectContext 0x282894000
Thread 3 Crashed:
0 libobjc.A.dylib 0x000000019ce066f4 object_getClass + 12
1 CoreData 0x000000018ee147a4 _PFObjectIDFastHash64 + 32
2 CoreFoundation 0x0000000188dba4f8 __CFBasicHashRehash + 992
3 CoreFoundation 0x0000000188dbe414 CFBasicHashRemoveValue + 2384
4 CoreFoundation 0x0000000188cd5ec0 CFDictionaryRemoveValue + 236
5 CoreData 0x000000018ed611c0 -[NSManagedObjectContext+ 299456 (_NSInternalAdditions) _forgetObject:propagateToObjectStore:removeFromRegistry:] + 124
6 CoreData 0x000000018ed406ec -[_PFManagedObjectReferenceQueue _processReferenceQueue:] + 860
7 CoreData 0x000000018ee5e198 __90-[NSManagedObjectContext+ 1335704 (_NSInternalNotificationHandling) _registerAsyncReferenceCallback]_block_invoke + 72
8 CoreData 0x000000018ee54410 developerSubmittedBlockToNSManagedObjectContextPerform + 164
9 libdispatch.dylib 0x000000018898cac8 _dispatch_client_callout + 20
10 libdispatch.dylib 0x0000000188993c08 _dispatch_lane_serial_drain + 580
11 libdispatch.dylib 0x0000000188994734 _dispatch_lane_invoke + 408
12 libdispatch.dylib 0x000000018899e528 _dispatch_workloop_worker_thread + 708
13 libsystem_pthread.dylib 0x00000001d0360908 _pthread_wqthread + 276
14 libsystem_pthread.dylib 0x00000001d036777c start_wqthread + 8

I have Same issue. Does anyone have a solution
I found if remove some core data index. Crash will decrease, but still not resolved.

Why has this problem happened for so long, but the official did not reply ?

Hi, we've had the very same problem on an App that we inherited. After recompiling under Xcode 12 we started having this very same error every time there was a call to a moc. Ended with encaplusated every call in performBlock or performBlockAndWait fixed our problem. Hope this helps somebody.

We are observing the same issue on an app that was working fine before the latest release of iOS 14.6

For us ,the responsible code is :

[NSManagedObjectContext _disposeObjects:count:notifyParent:]

which is triggered when a user logs out of the app, and we reset every objects of our CoreData stack.

Hope there will be a fix some day, until then, we are going to go down the -com.apple.CoreData.ConcurrencyDebug 1 road and try to nest every CoreData call into a [NSManagedObjectContext performBlockAndWait:] block.

Sorry I'm late to the game but here's how to actually fix this issue.

The Apple Engineer was correct, you'll need to add this flag to your scheme.

-com.apple.CoreData.ConcurrencyDebug 1

Xcode->Scheme->Edit Scheme->Arguments Tab

With the flag enabled, your code will break every place there is a concurrency issue with Core Data. The likely fix for this is to, (As the engineer pointed out) use perform or performAndWait where your NSManagedObjectContext is called.

func save() {
    context.performAndWait {
        do {
           try context.save()
        } catch let error{
            // Handle Error
        }
    }
}

Crashed: NSManagedObjectContext 0x281b95d40 0 CoreFoundation 0x11f80 __CFBasicHashRehash + 728 1 CoreFoundation 0x248a4 CFBasicHashRemoveValue + 452 2 CoreFoundation 0xf418 CFDictionaryRemoveValue + 196 3 CoreData 0x21448 -[NSManagedObjectContext(_NSInternalAdditions) _forgetObject:propagateToObjectStore:removeFromRegistry:] + 120 4 CoreData 0x2101c -[_PFManagedObjectReferenceQueue _processReferenceQueue:] + 616 5 CoreData 0x21dd4 __90-[NSManagedObjectContext(_NSInternalNotificationHandling) _registerAsyncReferenceCallback]_block_invoke + 80 6 CoreData 0x2074c developerSubmittedBlockToNSManagedObjectContextPerform + 156 7 libdispatch.dylib 0x4300 _dispatch_client_callout + 20 8 libdispatch.dylib 0xb894 _dispatch_lane_serial_drain + 748 9 libdispatch.dylib 0xc3c4 _dispatch_lane_invoke + 380 10 libdispatch.dylib 0x17004 _dispatch_root_queue_drain_deferred_wlh + 288 11 libdispatch.dylib 0x16878 _dispatch_workloop_worker_thread + 404 12 libsystem_pthread.dylib 0x1964 _pthread_wqthread + 288 13 libsystem_pthread.dylib 0x1a04 start_wqthread + 8

Same problem here in iOS17, is there any solution please comment