> On Apr 12, 2015, at 6:38 PM, Fritz Anderson <[email protected]> wrote:
> 
> On Apr 12, 2015, at 11:28 AM, Dave <[email protected]> wrote:
> 
>> I’ve been using XCode 6.3 for about a day and I’ve had all kind of hangs 
>> with the dreaded Swirling TechniColor Pizza of Death.
>> 
>> I’ve now got a project that eveytime I open it it hangs XCode. I’ve forced 
>> quit XCode and tried to re-open but it hangs each time I try it?
> 
> A project of mine would make 6.3 beachball whenever it opened. I had a 
> playground loaded-up with sources and a few resources. When I deleted the 
> playground bundle (in the Finder), Xcode was able to reopen the project.
> 
> There was also an incident wherein Xcode took it upon itself to change the 
> encoding flags on a couple of source files from UTF-8 to UTF-16, without 
> changing the actual encoding (as far as I could tell). That led to outright 
> crashes (and CJK source files). That was half an afternoon spent with Git.
> 
> And it still scrolls randomly to the bottom of source files if they get above 
> about 200 lines and I’m editing something in the lower half. I find this 
> trying, though I suppose I am getting a lasting education on keeping my 
> source factored.
> 
> Yes, these should be reported, but my only thought at the time was to rescue 
> my day’s work, not preserving a failable case.

I found many of these problems, and did a little detective work.

Previously in 6.2 I had a bunch of Xcode plug-ins installed via Alcatraz.  
While many still worked correctly in 6.2, they caused an almost immediate SPOD 
upon Xcode launch.  Removing the offending plug-ins (via binary search) has 
restored my Xcode to stable again.

-- 
Glenn L. Austin, Computer Wizard and Race Car Driver         <><
<http://www.austinsoft.com>


 _______________________________________________
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