• State Resolved
  • Locked Locked
  • Replies 34 replies
  • Subscribers 57 subscribers
  • Views 5407 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Frequent CCS crashes with MacOS Sierra

Matthew Hall
Intellectual 435 points
Other Parts Discussed in Thread: CCSTUDIO

I have been using CCS 6.2.0 on OSX El Capitan (10.11) for a long time, with very stable results. I recently updated my OS to MacOS Sierra (10.12) and experience extremely frequent crashes of CCS. No changes have been made to my TI project(s).

The crashes seem to occur on every 2nd build of my project(s). E.g. I launch CCS > build stack + debug > build app + debug > CCS crashes > Relaunch CCS > build app + debug > build app + debug a 2nd time > CCS crashes. I've included my crash log from Mac OS below. 

This crash also occurs with CCS 6.1.3 and CCS 7.0.0 beta. I have tried reseting the Window Perspective. I have launched CCS w/ the -clean argument. I have also deleted the .metadata directory and re-imported my project(s). The issue persists.

I'm installing CCS 6.2.0 on another mac running MacOS Sierra (10.12) and will report on those results.

Additionally, the installer for CCS 7.0.0 beta is very unstable and crashed multiple times before I could get the installation to begin.

Crash log:

http://pastebin.com/hs587hxT

  • 0
    Intellectual 435 points

    Upon trying to install 7.0.0 to another Mac running Sierra, I got a failure. The reference number is 29074, for any TI staff that can look into that.

  • 0
    Intellectual 435 points
    CCS 6.2.0, running on another Mac w/ Sierra, works just fine. No crashes seen so far.
  • 0 in reply to Matthew Hall
    TI__Guru**** 173310 points

    Matthew,

    I believe none of the CCS releases, including 7.0 Beta, have been officially validated with Mac OS Sierra ( I think the plan is to validate before v7 final release). This has been noted in the CCS Download page for the 7.0 Beta. 

    We will see if we can reproduce the build issues with Sierra.

    You mentioned you got a failure when installing 7.0.0 to one of your machines. Could you please provide details about that failure and install logs?

  • 0 in reply to AartiG
    Intellectual 435 points

    I did see the note that 7.0.0 beta is not validated for Sierra. Both 6.1.3 and 6.2.0 crash with the same error (as 7.0.0) on Sierra, so I don't think it's a beta issue.

    I'll try to dig up the logs from the failed install.

  • 0 in reply to Matthew Hall
    TI__Guru**** 161615 points
    I have updated my macbook to Sierra. I have not yet had any luck reproducing the crash. One of our team members did look at the crash log and believes that this may be a bug in SWT. We are looking into if there is a patch from Eclipse available. Thank you very much for including the crash log.

    Regards,
    John
  • 0 in reply to JohnS
    Intellectual 435 points
    John,

    Thank you for the response. What is SWT? I did a clean install of MacOS Sierra (format HD, install MacOS, did NOT transfer any data from old installation). The crashes persist. Is there anything else I can try?
  • 0 in reply to Matthew Hall
    TI__Guru**** 161615 points

    Matthew,

    SWT is the Standard Widget Toolkit that is used by Eclipse for user interface development.

    The Eclipse bug is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=502711 if you are interested.  Not a whole lot of information in it.

    At this time I don't have anything else for you to try.   I am not sure why I don't see the issue on my Sierra.  It really sounds like this issue is hitting you hard and making your environment unusable.

    We are evaluating if we can create a fix ourselves with the information provided at the link above and include this with CCSv7 which is getting ready to ship very soon.  As we have not been able to reproduce this yet on our side would you be able to test out a fix if we can put one together?

    Regards,

    John

  • 0 in reply to JohnS
    TI__Guru**** 161615 points

    Matthew,

    We have prepared a patch for CCSv7 that hopefully will resolve the issue that you are seeing.  Could you try copying the attached file into your ccsv6/ccs_base/eclipse/plugins folder.  ".renamed" will need to be removed from the end of the filename.  I would suggest backing up the existing copy of the file.

    Once you have copied in the new file it would be best to start CCS with the -clean option.  To do this run ccstudio -clean  This will ensure that the new plug-in is picked up.

    Thank you for your patience with this.  Would you also be able to send a screen capture of your system software overview?  We would like to compare this with what we have to see if there is some difference that explains why we have not been able to reproduce the issue.

    org.eclipse.swt.cocoa.macosx.x86_64_3.105.0.v20160603-0902.jar.renamed

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 435 points

    Hey John,

    Thanks for the speedy updates and posting the issue on the eclipse bug tracker. If I launch Eclipse directly (/Applications/ti/ccs620/ccsv6/eclipse), instead of ccstudio, I do not encounter the crash. 

    I'm willing to try the fix as long as it's a separate installation. I don't want to change anything in the currently working version of eclipse. If you can guarantee that the fixed version doesn't touch the existing installation then I'd be happy to give it a spin.

    -Matt

  • 0 in reply to Matthew Hall
    Intellectual 435 points
    Can I install CCSv7 and apply the fix to that installation?
  • 0 in reply to Matthew Hall
    TI__Guru**** 161615 points
    Yes that would actually be best if you could download the CCSv7 RC1 and install it in a separate folder.

    John
  • 0 in reply to JohnS
    Intellectual 435 points

    I'll try that. Also, attached is my System Software Overview (identifying info removed).

  • 0 in reply to Matthew Hall
    TI__Mastermind 22060 points
    The installer crash should be fixed in RC2.
  • 0 in reply to danishinnis
    TI__Guru**** 161615 points
    I believe RC2 (release candidate 2) will be Friday so it may make sense to install that and then apply the patch to see if that resolves the issue. If it does we can incorporate that fix into RC3.
  • 0 in reply to JohnS
    Intellectual 435 points

    I'm installing RC2 as I type. I did see one (so far) crash of the RC2 installer. The crash log is attached.

    ccs700rc2_install_crash.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    Process: tclsh [39072]
    Path: /tmp/*/tclsh
    Identifier: com.bitrock.appinstaller
    Version: 7.0.0.00020 (7.0.0.00020)
    Code Type: X86 (Native)
    Parent Process: osx-intel [39049]
    Responsible: tclsh [39072]
    User ID: 501
    Date/Time: 2016-11-29 14:07:38.319 -0800
    OS Version: Mac OS X 10.12.1 (16B2657)
    Report Version: 12
    Anonymous UUID: D0E2D69C-F9DD-9A19-A291-B40269C15053
    Time Awake Since Boot: 18000 seconds
    System Integrity Protection: enabled
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread
    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY
    Termination Signal: Trace/BPT trap: 5
    Termination Reason: Namespace SIGNAL, Code 0x5
    Terminating Process: exc handler [0]
    Application Specific Information:
    *** Terminating app due to uncaught exception 'CALayerInvalidGeometry', reason: 'CALayer position contains NaN: [0 nan]'
    Application Specific Backtrace 1:
    0 CoreFoundation 0x9476412b __raiseError + 187
    1 libobjc.A.dylib 0x9ee466e6 objc_exception_throw + 273
    2 CoreFoundation 0x94764045 +[NSException raise:format:] + 133
    3 QuartzCore 0x98e80a4c _ZN2CA5Layer12set_positionERKNS_4Vec2IdEEb + 190
    4 QuartzCore 0x98e80bd1 -[CALayer setPosition:] + 39
    5 QuartzCore 0x98e8129a -[CALayer setFrame:] + 786
    6 CoreUI 0x9bb6699c _ZN20CUICoreThemeRenderer26MakeOrUpdateScrollBarLayerEPK13CUIDescriptoraPP7CALayer + 1252
    7 CoreUI 0x9bb62ac8 _ZN20CUICoreThemeRenderer19CreateOrUpdateLayerEPK13CUIDescriptorPP7CALayer + 1644
    8 CoreUI 0x9bae45a8 _ZN11CUIRenderer19CreateOrUpdateLayerEPK14__CFDictionaryPP7CALayer + 184
    9 CoreUI 0x9bae6e68 CUICreateOrUpdateLayer + 217
    10 AppKit 0x92647064 __45-[NSAppearance _createOrUpdateLayer:options:]_block_invoke + 26
    11 AppKit 0x930380a2 -[NSAppearance _callCoreUIWithBlock:options:] + 1188
    12 AppKit 0x9303963b -[NSCompositeAppearance _callCoreUIWithBlock:options:] + 147
    13 AppKit 0x92647043 -[NSAppearance _createOrUpdateLayer:options:] + 84
    14 AppKit 0x928a703d -[NSScrollerImp _animateToRolloverState] + 312
    15 AppKit 0x9286914e __49-[NSScrollerImp _installDelayedRolloverAnimation]_block_invoke + 718
    16 AppKit 0x9273967d -[NSScrollerImp _doWork:] + 23
    17 Foundation 0x95d80294 __NSFireDelayedPerform + 501
    18 CoreFoundation 0x94658986 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22
    19 CoreFoundation 0x9465849d __CFRunLoopDoTimer + 1213
    20 CoreFoundation 0x94657f3e __CFRunLoopDoTimers + 350
    21 CoreFoundation 0x9464fb00 __CFRunLoopRun + 2192
    22 CoreFoundation 0x9464f00a CFRunLoopRunSpecific + 506
    23 CoreFoundation 0x9464edfb CFRunLoopRunInMode + 123
    24 libtcl8.6.dylib 0x001dde6a Tcl_WaitForEvent + 298
    25 libtcl8.6.dylib 0x00191f7e Tcl_DoOneEvent + 262
    26 libtcl8.6.dylib 0x00159068 Tcl_VwaitObjCmd + 183
    27 libtcl8.6.dylib 0x000f5350 Dispatch + 48
    28 libtcl8.6.dylib 0x000f2a6f TclNRRunCallbacks + 70
    29 libtcl8.6.dylib 0x000f3b3d TclEvalEx + 1597
    30 libtcl8.6.dylib 0x00185ff3 Tcl_FSEvalFileEx + 543
    31 libtcl8.6.dylib 0x0018c7a8 Tcl_MainEx + 1155
    32 tclsh 0x00002a3f main + 41
    33 libdyld.dylib 0x9f6983b5 start + 1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Matthew Hall
    Intellectual 435 points
    After attempting to install RC2 a few times (all resulting in the same crash, mentioned and logged above), I tried replacing my current installation's plugin file with the one you guys provided, but the directory and file do not exist. Under my ccs_base/eclipse dir I only have one subdir titled 'features'

    Any additional instructions on how to patch the swt file?
  • 0 in reply to Matthew Hall
    TI__Genius 15190 points
    Hi Matthew,
    Unfortunately, my colleague provided you with incorrect path information. The path should be
    ccsv7/eclipse/Eclipse/Contents/Eclipse/plugins If you use Finder then ccsv7/eclipse will show that there are two applications ccstudio and eclipse. Both are OSX specific directories that conform to OSX way of packaging applications, thus you need to click on Eclipse and then from Action button in Finder's toolbar choose "Show Package Contents". This would allow you to show package contents and navigate to path mentioned above. Please let us know if this works.

    Martin
  • 0 in reply to Matthew Hall
    TI__Mastermind 22060 points

    Unfortunately, the fix didn't make it into RC2. I'm sorry for the inconvenience.

  • 0 in reply to danishinnis
    Intellectual 435 points

    What is the best way to launch ccstudio w/ the '-clean' flag?

  • 0 in reply to Matthew Hall
    TI__Genius 15190 points

    You would need to open Terminal and navigate to where CCS is installed and then cd into ccsv7/eclipse/Ccstudio.app/Contents/MacOS then you should be able to execute "./ccstudio -clean" ccstudio launcher should be in that directory

    Martin

  • 0 in reply to MartinS
    Intellectual 435 points

    I replaced the .jar file w/ the patched version (and removed the '.renamed' tag). After that I removed the old .jar file and ran './ccstudio -clean' which launched CCS but failed w/ the attached log.

    1480709676496.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    !SESSION 2016-12-02 12:14:36.339 -----------------------------------------------
    eclipse.buildId=4.5.1.M20150904-0015
    java.version=1.8.0_66
    java.vendor=Oracle Corporation
    BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
    Framework arguments: -product com.ti.ccstudio.branding.product
    Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.ti.ccstudio.branding.product -clean
    !ENTRY org.eclipse.osgi 4 0 2016-12-02 12:14:42.094
    !MESSAGE An error occurred while automatically activating bundle org.eclipse.ui.workbench (515).
    !STACK 0
    org.osgi.framework.BundleException: Error starting module.
    at org.eclipse.osgi.container.Module.doStart(Module.java:580)
    at org.eclipse.osgi.container.Module.start(Module.java:439)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
    at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
    at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
    at java.lang.Class.getConstructor0(Class.java:3075)
    at java.lang.Class.newInstance(Class.java:412)
    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
    Caused by: java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
    at java.lang.Class.getConstructor0(Class.java:3075)
    at java.lang.Class.newInstance(Class.java:412)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.loadBundleActivator(BundleContextImpl.java:755)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:706)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
    at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
    at org.eclipse.osgi.container.Module.doStart(Module.java:571)
    ... 32 more
    Caused by: java.lang.ClassNotFoundException: org.eclipse.swt.SWTError cannot be found by org.eclipse.ui.workbench_3.107.0.v20150825-2206
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    ... 41 more
    Root exception:
    java.lang.NoClassDefFoundError: org/eclipse/swt/SWTError
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Matthew Hall
    Intellectual 435 points
    This was on ccs 6.2.0, FYI. Does the patched .jar file work for v6?
  • 0 in reply to Matthew Hall
    TI__Genius 15190 points
    no, this file will only work with CCS v7, any build should work. You should get a file replace/overwrite pop up once you remove the .remove extension and try to save file that John provided. If you did not rename the original. In essence we are trying to replace one of the existing eclipse plugin files with a modified version.

    6.2 and 7.0 use different version of eclipse thus those plugin names are different. You would need to put back original 6.2 jar file in your 6.2 installation directory to get it back to a working state.

    Martin
  • 0 in reply to MartinS
    Intellectual 435 points
    Hi Martin,

    Thanks for the response. Can your team provide a patched .jar file for 6.2.0? As mentioned above, I'm unable to install 7.0.0 rc2 due to a known issue that hasn't been fixed yet.
  • 0 in reply to Matthew Hall
    TI__Genius 15190 points
    Hi Matthew,
    I'll try to get you patched file on monday.

    martin
  • 0 in reply to MartinS
    Intellectual 435 points
    Thanks. I look forward to trying it out.
  • 0 in reply to Matthew Hall
    TI__Genius 15190 points

    Hi Matthew,

    Please find attached .jar file that should work with CCS 6.2. Instructions for patching are the same as for 7.0.

    org.eclipse.swt.cocoa.macosx.x86_64_3.104.1.v20150825-0743.jar.renamed

  • 0 in reply to MartinS
    Intellectual 435 points
    I've swapped the new file in and CCS seems to be stable. I'll keep using it throughout the day and report back with any new details.
  • 0 in reply to Matthew Hall
    Intellectual 435 points
    The issue appears to have been fixed w/ the patched .jar file for v6.2.0.
  • 0 in reply to Matthew Hall
    TI__Genius 15190 points

    Thank you for getting back to us. 

    Martin

  • 0 in reply to Matthew Hall
    Expert 1085 points
    I have been fighting this problem for weeks and my only option was to save often and restart CCS after crash.
    The crash would occur on the 2nd build with a GUI related bug as it seemed from the report after the crash.
    I am using 6.2.0 on Sierra 10.12.1 and it seems to have fixed the issue.

    Thank you very much!!!
    I can now debug code without constant crashes on builds!

    I would not be the first to jump at new OS versions but as I also do iOS development with Xcode and the latest OSX version is often pushed on developers as a requirement for the latest Xcode, to support the latest iPhone devices.

    I have also had crashes while highlighting large quantities of text and then deleting, so I will see if this also fixes that problem.
    I have one more issue with the way the settings for "use spaces instead of tabs" is not being obeyed. I am a space type person and it is driving me nuts when indents all turn into tabs. I will make a new post or search for information on this bug at a later time.
  • 0 in reply to AllanD
    Expert 1704 points
    Ditto, thanks for posting the patch. The crash was getting aggravating.
  • 0 in reply to MartinS
    Prodigy 90 points

    @Ti employees:

    Could you provide one Post describing all steps needed to fix the issue (file to download, directory to put it in, how to use -clean)? I tried to grab the different information and corrections from the different posts, but I'm afraid I didn't make it right, as I still encounter the problem.

  • 0 in reply to Malte Ebner
    Expert 1704 points

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/556117/2038069#2038069

    That post has the file you need, but I agree that the TI employees should probably write up a summary post and mark it as the answer.