Version? The source kit crashes were mostly fixed by 6.3 and 7 hasn't been bad, 
couple of beach balls on the whole system but no source kit crashes for a 
while. 



> On 14 Jun 2015, at 22:14, William Squires <[email protected]> wrote:
> 
>  Is anyone else having a problem with SourceKit crashing during editing of 
> Swift source? It seems to happen most often if I'm in the middle of typing a 
> line that's not syntactically correct (yet). For example, I was typing in 
> this:
> 
> class FontSizesViewController: UITableViewController
> {
>  var font: UIFont!
>  private var pointSizes: [CGFloat]
>    {
>    struct Constants
>      {
>      static let pointSizes: [CGFloat] = [9, 10, 11, 12, 13, 14, 18, 24, 36, 
> <- and it would usually crash right about here
> 
>  The remainder of the line was:
> 
> 72, 96, 144]
> 
> but continued typing kept popping up the "SourceKit has crashed" dialog. I 
> kept having to save, exit Xcode, relaunch Xcode, and type some more until it 
> crashed again (usually after only 1 or 2 more characters typed in.) Once I 
> managed to type in the closing ']', it stopped crashing.
>  It would be more helpful if you (as the Xcode user) could set a programmatic 
> delay between typing the last character and Xcode trying to syntax check the 
> source. Then I could set it for 5-10 seconds or so and see if that helped. 
> Hopefully this will be a feature in Xcode 7...
> 
> 
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/xcode-users/rols%40rols.org
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to