RTC 6.0.4 Client Crashes on Mac OS X 10.12.5
When I try to start the 6.0.4 Client is just crashes. My 6.0.2 Client works just fine. Any ideas? Here is a snippet of the error dump:
Process: eclipse [5812]Path: /Volumes/VOLUME//Eclipse.app/Contents/MacOS/eclipseIdentifier: org.eclipse.eclipseVersion: 3.8 (3.8)Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: eclipse [5812]User ID: 501
Date/Time: 2017-06-22 14:58:23.038 -0400OS Version: Mac OS X 10.12.5 (16F73)Report Version: 12Anonymous UUID: F7A36B99-92A7-8CE5-8B62-CF893C6231BF
Sleep/Wake UUID: F17311C6-DACE-4EEC-8EC4-530DCEF02239
Time Awake Since Boot: 20000 secondsTime Since Wake: 19000 seconds
System Integrity Protection: enabled
Notes: Translocated Process
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000003cException Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11Termination Reason: Namespace SIGNAL, Code 0xbTerminating Process: exc handler [0]
VM Regions Near 0x3c:-->__TEXT 0000000100000000-0000000100004000 [ 16K] r-x/rwx SM=COW /var/folders//Eclipse.app/Contents/MacOS/eclipse
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread0 com.apple.CoreFoundation 0x00007fff870d9fb4 CFBundleGetFunctionPointerForName + 361 org.eclipse.eclipse 0x00000001000030bd findSymbol + 662 org.eclipse.eclipse 0x00000001000018be original_main + 15723 org.eclipse.eclipse 0x0000000100001f7d main + 12304 org.eclipse.eclipse 0x0000000100001158 start + 52
Thread 1:0 libsystem_pthread.dylib 0x00007fff9ce3c070 start_wqthread + 0
Thread 2:0 libsystem_pthread.dylib 0x00007fff9ce3c070 start_wqthread + 0
Accepted answer
Both RTC 6.0.3 and 6.0.4 crash on my Mac, but both can be launched this way.
1. Right-click on the Eclipse application and choose Show Package Contents.
2. Get into the folder Contents, then MacOS, where you can see the eclipse Unix executable.
3. Double-click on the eclipse executable.
If everything goes to plan, you should see the splash screen and it should work as usual. You have to launch it this way every time though.