Xcode 7 / 7.0.1 Unexpected quit frequently - Exception Code - KERN_INVALID_ADDRESS

Im having the same problem. Xcode frequently quits and for me, this happens when I am working in the interafce builder. Any one else having this problem?

Same here. XCode 7.0.1 on El Capitan. IB is really unstable when manipulating objects on forms. Especially when touching controls in the attributes inspector. Crashes frequently. The last crash I literally clicked on an image centered on LaunchScreen.storyboard, and *that* crashed Xcode with __vImageCopyBuffer_block_invoke at the top of the stack dump as OP above.

Haven't seen any crashing when using code editor or any other features--only in IB. I'm getting in the habit of hitting command-S before every small change in IB and hoping for relief in a forthcoming update.

Today I dragged XCode to trash, reinstalled from the app store. Didn't help, unfortunately. Same problems after.

Have been sending the crash reports on every occurrence, hopefully the telemetry I'm sending will help.

Yeah, it happens to me all the time. Happened in XCode 7.0, XCode 7.0.1, and now in XCode 7.1 after upgrading today. I'm running OS 10.11.1 as of today too. It's really frustrating. It will crash on me mulitple times in any given workday. It always happens to me when working in IB, just editing properties (usually with the drop downs) mostly things like setting the color, changing the font styles, etc. It's almost unusable, in my view. I can't believe Apple released this with a bug this big in it, and it's on-going over multiple versions of XCode 7. I've filed bug reports with crash logs and they keep saying it's a "Duplicate" and as of today the status is still "Open".

Interesting note, it only happens on my iMac 5K Retina, Late 2014, with Core i7 4.0ghz, 32gb mem, 4GB AMD M295 video, 1 TB SSD. It has never happened with I run it on my Early 2014 Macbook Pro with Core i7 2.6ghz, 16gb mem, and 1 TB SSD. Both are running OS X El Capitan.

So my previous crashes were with the same vImageCopyBuffer error. After upgrading to 10.11.1 and XCode 7.1, the crashes I've had today have changed and are now this:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGILL)

Exception Codes: KERN_INVALID_ADDRESS at 0x00007ff7512f98d8

Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0x7ff7512f98d8:

MALLOC_TINY 00007fe063800000-00007fe068c00000 [ 84.0M] rw-/rwx SM=PRV

-->

Stack Guard 00007fff4c8f9000-00007fff500f9000 [ 56.0M] ---/rwx SM=NUL

Application Specific Information:

ProductBuildVersion: 7B91b

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.QuartzCore 0x00007fff85bf16bb CA::Render::Shmem::copy_image(CGColorSpace*) + 99

1 com.apple.QuartzCore 0x00007fff85bf15f9 CABackingStoreGetFrontTexture(CABackingStore*) + 61

2 com.apple.QuartzCore 0x00007fff85bf159a CABackingStoreRetainFrontTexture + 30

3 com.apple.QuartzCore 0x00007fff85be0495 -[CALayer(CALayerPrivate) _copyRenderLayer:layerFlags:commitFlags:] + 557

4 com.apple.QuartzCore 0x00007fff85bdfdfd CA::Context::commit_layer(CA::Layer*, unsigned int, unsigned int, void*) + 103

5 com.apple.QuartzCore 0x00007fff85bdfd2a CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 330

6 com.apple.QuartzCore 0x00007fff85bdfcaa CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 202

7 com.apple.QuartzCore 0x00007fff85bdfcaa CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 202

8 com.apple.QuartzCore 0x00007fff85bdfcaa CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 202

9 com.apple.QuartzCore 0x00007fff85bdfcaa CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 202

10 com.apple.QuartzCore 0x00007fff85bdfcaa CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 202

11 com.apple.QuartzCore 0x00007fff85bdfcaa CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 202

12 com.apple.QuartzCore 0x00007fff85bdfcaa CA::Layer::commit_if_needed(CA::Transaction*, void (*)(CA::Layer*, unsigned int, unsigned int, void*), void*) + 202

13 com.apple.QuartzCore 0x00007fff85bde2d2 CA::Context::commit_transaction(CA::Transaction*) + 1766

14 com.apple.QuartzCore 0x00007fff85bdd94c CA::Transaction::commit() + 508

15 com.apple.QuartzCore 0x00007fff85be913b CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 71

16 com.apple.CoreFoundation 0x00007fff84063097 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23

17 com.apple.CoreFoundation 0x00007fff84063007 __CFRunLoopDoObservers + 391

18 com.apple.CoreFoundation 0x00007fff84041fe8 CFRunLoopRunSpecific + 328

19 com.apple.HIToolbox 0x00007fff905fed55 RunCurrentEventLoopInMode + 235

20 com.apple.HIToolbox 0x00007fff905fea97 ReceiveNextEventCommon + 184

21 com.apple.HIToolbox 0x00007fff905fe9cf _BlockUntilNextEventMatchingListInModeWithFilter + 71

22 com.apple.AppKit 0x00007fff8922cd96 _DPSNextEvent + 1067

23 com.apple.AppKit 0x00007fff8922c1c5 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454

24 com.apple.dt.DVTKit 0x000000010fb155fc -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 247

25 com.apple.AppKit 0x00007fff89220d28 -[NSApplication run] + 682

26 com.apple.AppKit 0x00007fff891e9fbe NSApplicationMain + 1176

27 libdyld.dylib 0x00007fff8afa55ad start + 1

Interesting, it happens a lot with me especially since today and the update to 7.1

It crashes literally on any modification of any element in IB (especially if it has custom font, event the basic ones like Georgia).

It happens mainly on my workhorse, aka the iMac Retina, same configuration as above (and the Ram is from Apple, not user serviced one)

Now, I'm afraid of updating the other computers.

Follow Up to this post of mine. Still having the continual crashes, but I see both the one I posted above sometimes, and others are the one with the vImageCopyBuffer_block_invoke like the original poster.

Guess developers running iMac Retinas don't count and aren't worth spending the time to fix a bug that makes a big chunk of Apple's development tool unusable. 😟 How is it that this kind of major bug made it through three revisions of XCode thus far without being fixed? I thought for sure it would be fixed in XCode 7.1, and as you observed it seems to be worse in 7.1. I can't edit any more than two or three font changes or color changes without having it crash and have to "Reopen".

Honestl, I wonder if Apple is still caring at all about developers?

While I like the new "options" in Xcode, it's useless if the tool itself is unusable ... I can't spend 1 hour at work just to change the font size on one element.

And it's not only on the retina screen (I have a non-retina screen attached, and editing on it doesn't help either). I've been working quite stably on this Retina since its release day, if we don't count the fiasco of 6.3 (that was fixed a week later in 6.3.1) which forced the whole team to just drop the iOS version and focus on Android on that week.

It shouldn't be that hard to at least find the bug, it happens when Xcode changes the layout XML and it has to be re-rendered (refreshed) on screen.

One thing that can "ease" the crashes a bit (if you don't use preview), is to disable the "Automatically Refresh Views" option from Editor menu.

Hope it helps.

Yep, even with Xcode 7.1 I also affected with this problem.

So now, my workaround (tested by myself) is try to press Command-S (save) frequently when I changed things on the IB (GUI) side, I noticed this reduce the chance the Xcode crash incident. So the frequency of Xcode crash I noticed is from "usually crash" to "sometime crash" instead 😝

This is latest from Apple (replied to the Bug Report case)

The original report on the issue, Bug ID 22266225, was closed and the resolution is “fixed in El Capitan 01.11.2 build 15C31”. That build is not available yet, so please check the Developer web site for its availability.

Got this update today (beta) and it works 🙂 it really works!!!