Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-07 Thread Motti Shneor
Hi Dave and thanks for the reply. As you can see in the stack - there isn’t actually any “code” per-se that runs at that time. Here is the actual method that fails: // Show the measurement browser panel, in which user can review existing measurements for the selected sample.

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Motti Shneor
Well - 2AM and I finally resolved it. I also think I understand why the strange recursion occurs This double-layer binding of content-array of one NSArrayController to the arrangedObjects of another NSArrayController (who’s bound to an ordered relation of…. ) made loading to occur like this.

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Sandor Szatmari
If you can, can you establish the binding programmatically after launch? If so, does the program crash once the bindings are re-established? … considering if it is a launch issue or more systematic? Sandor > On Nov 4, 2018, at 17:25, Motti Shneor wrote: > > Well, thanks Dave, Hunter,

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Motti Shneor
Well, thanks Dave, Hunter, Richard and the rest. I followed each of your suggestions, and I finally found the culprit. A single binding, rather a nifty one, which I don’t know how to do better — Maybe you can help. Removing this binding (alas losing functionality) window opens instantly,

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Dave Fernandes
> On Nov 4, 2018, at 2:24 PM, Motti Shneor wrote: > > Hi Dave and thanks for the reply. > > As you can see in the stack - there isn’t actually any “code” per-se that > runs at that time. Here is the actual method that fails: > > As for modifying the persistent store - I guess I don’t

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Dave Fernandes
Does your code modify anything in the persistent store during loading (NSManagedObjectContextDidChangeNotification)? Maybe it is rounding some values for display? This might cause infinite recursion with bindings. > On Nov 4, 2018, at 2:42 AM, Motti Shneor wrote: > > Thanks Richard. > > The

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Hunter Hillegas
> On Nov 4, 2018, at 12:42 AM, Motti Shneor wrote: > > 3. I tried to build with Xcode 9.4.1 (MacOS SDK 10.13) then with Xcode 10 > (MacOS SDK 10.14) - same thing. I only have my MacOS 10.13 to try running on. > I cannot run the original Xcode (8.x) with which the production version was >

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Hunter Hillegas
___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription:

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Richard Charles
> On Nov 4, 2018, at 1:42 AM, Motti Shneor wrote: > > I just do not know how to go about resolving this. Here is another idea. Remove your bindings one at a time. Perhaps it is just one binding that is causing the problem and then you can perhaps track it from there. It looks like this may

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-04 Thread Motti Shneor
Thanks Richard. The data is OK. Not corrupt. I can import and export it to .csv, and I do run several sanity test (heavy calculations based on that data pass OK and provide expected results). Most important - the production build of the software (built half year ago), opens the same database

Re: Need a direction. App crash in CoreData while loading a window's nib

2018-11-03 Thread Richard Charles
> On Nov 3, 2018, at 2:47 PM, Motti Shneor wrote: > > Can anyone suggest a way to start bisecting the issue or an idea where to > look for? You may have bad or corrupted data in your core data persistent store. Save the file out as an xml and see if you find anything suspicious. You could