> On Nov 4, 2018, at 12:42 AM, Motti Shneor <motti.shn...@me.com> 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 > built. It won’t run on my OS.
Apple does provide older versions of macOS that you can download and run in something like vmWare or Parallels if you want to try running Xcode 8 - it would be interesting to see what happens there. Looks like Xcode 8 will run on Sierra which you may be able to get via this link: https://itunes.apple.com/gb/app/macos-sierra/id1127487414?mt=12 AppKit and other libraries do often behave slightly differently based on the version they are built and run against, to maintain compatibility. So it’s possible that a build from Xcode 8 would hit slightly different code paths in the frameworks than Xcode 9 or 10. > Another idea I had — I’m using AutoLayout in the .xib file. Maybe — for > pre-caculating the “needed” space for some table column, it needs to know in > advance the widths of all texts it should ever display there, hence it is > forced to scan the whole data via some bindings before it can finally show > the table? I’m much more fluent in UIKit than AppKit but I’d be surprised if this was the case - would make Core Data faults, one of the best features for dealing with large data sets, basically worthless when used with NSTableView. That said, you could try profiling this in Instruments to see what it’s doing in that period of time right before it crashes when it’s burning CPU. _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
