Ruslan Skorb

I started testing this change and can confirm that **PSC -> Main Context** Core Data stack setup prevents the loading all objects directly in memory at the time the FRC...

I found two problems at the moment. The more the number of fetched objects, the more noticeable each of them. Each of these problems belongs to `ListMonitor`. 1) When the...

> Does this happen with the develop branch as well? No, this only happens when **Main Context** is connected directly to **PSC**.

@JohnEstropia It works the same even if we replace `observerForDidSaveNotification` by `automaticallyMergesChangesFromParent` (available on iOS 10). And, I tested saving transactions asynchronously.

@JohnEstropia In my previous comment I meant that `NSManagedObjectContext.object(with:)` call in `NSManagedObjectContext+Setup` does not cause those lags. I tried to comment out this code but nothing has changed. After that...

I'm here again :-] > I'm inclined to think so. Actually I don't see how NSFRC will find updates to its objects without any sort of fetching. NSFRC gets those...

> All your observations are from the `prototype/mainContextToPSC` branch, is that correct? Yes, it is. > As I can see in Instruments after merging when we are accessing an object...

@evadne Yes, I'm open for merging my changes back upstream. Can I help with something else? :)

Hi @nnhubbard, I think you might be interested in this - https://github.com/ruslanskorb/RSDayFlow/issues/23 Sincerely, Ruslan

Hey, @erik-bershel. I have a [project](https://github.com/ruslanskorb/RSKImageCropper/tree/develop) for you where this error occurs. [Failed job logs.zip](https://github.com/actions/runner-images/files/14890964/logs_22479285857.zip) Let me know if there is anything else I can do to help resolve this...