[ISSUE] - Closing project error

The following crash/error log was created when I closed a project in Nuendo 6.5.
NUENDO_6.5_Yosemite_error.zip (24 KB)
Using Yosemite with a brand new iMac. MR816csx interface.

This same thing happens a lot. Not sure if there is a solution.

The important parts of this file to note are:

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

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000011d7b3e28

VM Regions Near 0x11d7b3e28:
    Image IO               000000011d645000-000000011d794000 [ 1340K] rw-/rwx SM=PRV  
    MALLOC_LARGE           000000011d8cb000-000000011d900000 [  212K] rw-/rwx SM=PRV  

Application Specific Information:
Performing @selector(select:) from sender SMTGCocoa1406046916_MenuItem 0x6080000c3cd0


Thread 61:

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x000000011d7b3e08  rbx: 0x0000600000394290  rcx: 0x00000001054bae78  rdx: 0x0000000000000003
  rdi: 0x00007fff776582a8  rsi: 0x0000600000394290  rbp: 0x00007fff5fbfbe80  rsp: 0x00007fff5fbfbe70
   r8: 0x00000001054bae00   r9: 0x000000000000003f  r10: 0x000000000000000f  r11: 0x0000000000000000
  r12: 0x00007fff77658280  r13: 0x0000600000394290  r14: 0x00007fff776582a8  r15: 0x00006080008fcf10
  rip: 0x00007fff8849ef2b  rfl: 0x0000000000010206  cr2: 0x000000011d7b3e28
Logical CPU:     2
Error Code:      0x00000004
Trap Number:     14

This suggestion is not the root cause of the problem, but. Have you tried the following maintenance on your computer:
[1] Repair Permissions on the system drive
[2] Verify system disk (and repair if needed)
[3] Run a good RAM diagnostic program and maybe Reseat the RAM

PS - this might help - http://www.macworld.com/article/2362040/do-you-have-bad-ram-how-to-find-it-and-how-to-fix-it.html

That Nuendo’s not ready for Yosemite just might have something to do with it as well!


Thanks for the replies. I’ve repaired permissions already. I’ll try verifying the system disk. What’s a proper RAM diagnostics program to run? I’ll be a bit irritated if they shipped this computer with faulty RAM.

see my post three above this one. Given it is a new mac by the sounds of it, boot from your recovery partition is likely all you need to do to do a thorough test. I don’t expect it to be RAM but I have found that to be a more common problem than it should be and it is always good to rule that out.