Xcode 4.5.2 continues to crash on Mac OS X Mountain Lion?

Question

I am using Xcode with mac os x lion and I continued to receive an error message while trying to test my application on my ios device. I formatted my computer and got to the mountain lion and canceled all the certificates and regulations of the Apple developer and started from scratch.

Now I no longer get the error, but when I click the "Run Xcode" button. I have seen other people having the same problem. I tried installing the tools in Xcode and reinstalling Xcode, but nothing works. I even tried other applications. Xcode even crashes when I look at the settings or just by accident, but it is unsuitable. I tried what people suggested, but I think maybe this is an update for Mountain Lion.

Anyone have thoughts on what I can do to fix this? Thanks guys and I ran into the Xcode error below.

---

Process: Xcode [3082] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 4.5.2 (1847) Build Info: IDEApplication-1847000000000000~5 App Item ID: 497799835 App External ID: 11823664 Code Type: X86-64 (Native) Parent Process: launchd [120] User ID: 501 Date/Time: 2012-11-11 23:59:26.948 -0500 OS Version: Mac OS X 10.8 (12A239) Report Version: 10 Interval Since Last Report: 12182 sec Crashes Since Last Report: 7 Per-App Interval Since Last Report: 2713 sec Per-App Crashes Since Last Report: 7 Anonymous UUID: 08010D4F-F690-41D3-BFD3-D1ECE072975C Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff50fe0ff8 VM Regions Near 0x7fff50fe0ff8: MALLOC_SMALL 00007fb59e800000-00007fb59f800000 [ 16.0M] rw-/rwx SM=PRV --> STACK GUARD 00007fff4d7e1000-00007fff50fe1000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0 Stack 00007fff50fe1000-00007fff517e1000 [ 8192K] rw-/rwx SM=COW thread 0 Application Specific Information: ProductBuildVersion: 4G2008a objc[3082]: garbage collection is ON Performing @selector(performRunAction:) from sender IDERunPauseContinueToolbarButton 0x4023116a0 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.dt.IDE.IDEInterfaceBuilderCocoaIntegration 0x000000011621a96e -[NSClipView(IBWorkaround12332156) ibSwizzledNSClipViewWorkaround12332156UpdateConstraints] + 21 1 com.apple.dt.IDE.IDEInterfaceBuilderCocoaIntegration 0x000000011621a9fc -[NSClipView(IBWorkaround12332156) ibSwizzledNSClipViewWorkaround12332156UpdateConstraints] + 163 2 com.apple.dt.IDE.IDEInterfaceBuilderCocoaIntegration 0x000000011621a9fc -[NSClipView(IBWorkaround12332156) ibSwizzledNSClipViewWorkaround12332156UpdateConstraints] + 163 3 com.apple.dt.IDE.IDEInterfaceBuilderCocoaIntegration 0x000000011621a9fc -[NSClipView(IBWorkaround12332156) ibSwizzledNSClipViewWorkaround12332156UpdateConstraints] + 163 4 com.apple.dt.IDE.IDEInterfaceBuilderCocoaIntegration 0x000000011621a9fc -[NSClipView(IBWorkaround12332156) ibSwizzledNSClipViewWorkaround12332156UpdateConstraints] + 163 5 com.apple.dt.IDE.IDEInterfaceBuilderCocoaIntegration 

Answer 1

I had a problem when multiple Xcode instances were running in the background, which caused Xcode to crash. I'm not sure if this will help or not, but you can try the following in the terminal.

 alias findp="ps -axww | grep $*" 

These are just a few abbreviations.

see what it does.

 findp Xcode 

If you have a huge list of instances returning for this call when you are not actually using Xcode, then you have a bunch of xcode processes with orphaned backgrounds. The simulator will also contain xcode instances, so you will also need to close this.

In any case, if you have a problem, you will see repons along the lines

  7645 ?? 0:00.12 /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.0.sdk/System/Library/Frameworks/Accounts.framework/accountsd 

you can kill them with

 kill -9 7645 

Not sure if this will help you or not, but it saved me many times when xcode played stupid buggers with me.

Answer 2

Okay, so I know that this is not an ideal solution, but what I found for me is to download iOS 5.0 and 5.1 SDK to run testing through a simulator (yes, I know, this creates a problem, not the ability to run tests through the current simulator ...), but I can just run my application on my prepared iPhone device for testing in iOS 6.0

Simulator 6.0 seems to be the culprit in this disaster. Also, if you have the same setup as mine, then you will need to know that you need to stop the application before trying to start it again, or it will crash. In addition, if you use a simulator (5.1 or 5.0), you need to be sure that you will not only stop your application, but also completely close the simulator. Otherwise, it may lead to another failure.

All the errors that I encountered during the installation of the current Xcode 4.5.2 environment led to the same error message that you received above.

Hope this helps!

-d3v1lman1337