I've been running into this lately. I had SourceKitService eating 162G of memory (on an iMac with 32G of RAM). I feel like it is triggered by confusion of the compiler in certain cases. Out of frustration, and wanting to do something different, I got into a shell, and did "kill -1" to the SourceKitService. To my great delight, it stopped and restarted, and is now using a reasonable amount of memory.Dunno if this fixed things for all time, probably not, but it's nice to know there is some possible workaround.
hacksaw
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Awesome, works for me. Reads slightly cleaner, too. But yeah, can't think why they are are different. I'd love to know... I think I'll ask on the Swift forums.
In any case, thanks!
Filed: FB7802730
For me, this version keeps asking if I want to close the workspace whenever I come back to the machine in the morning. (I don't turn off my machine at night).
Not a crash, but very odd.
I was just using the program. Mostly I want to know what being in a penalty box means. Obviously it's not urgent, in fact I haven't seen it any time lately, so maybe a macOS upgrade changed things. I found it when I was looking to understand what the plugin I was developing was doing.