• State Resolved
  • Locked Locked
  • Replies 20 replies
  • Subscribers 56 subscribers
  • Views 3379 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Code Compose 6 Mac OSX locksup often, studders

Kevin Stallard
Intellectual 445 points


CCSLogsFreezing.zip

Right clicking, performing operations, building.  Everything seems to cause CCS to hesitate, lockup for a bit.  The spinning pinwheel is a regular part of my life.

I've dug around, one solution recommended deleting .metadata and starting over.  I've that. 

I'm not so much asking that you solve my problem, but I would like to identify the plugin or subsystem that is halting.

I've attached my log files here.  Thank you for your help.  Ideas are appreciated.

Thanks

Kevin

  • 0
    Intellectual 445 points

    BTW: Just want to make sure you guys and gals know how much I love having a MacOSX version of CCS. Thank you for all your hard work on it.

  • 0
    Intellectual 445 points

    CCSLogsFreezing_30seconds.zip

    I cleaned out .metadata one more time, and took another log snapshot just after i tried to right click->build.  I've attached a screen shot as well.  It took almost 30 seconds for the pinwheel to go away and for the build to commence.  Even after the build finished, the pinwheel reappeared and it locked up again for several seconds.

    Sorry if I sound like I am complaining....I added a picture, but alas...it doesn't show the pretty beach ball...

  • 0 in reply to Kevin Stallard
    TI__Guru**** 173310 points

    Kevin,

    Can you also provide us with the project you are building? It looks like it only contains pinmux.c and opinmux.h. Is that correct?

    Does this slow build behavior occur when building any project in this workspace? And how is the performance when you are editing code, modifying project settings, etc?

  • 0 in reply to AartiG
    Intellectual 445 points
    Yes, I'll send you the project over. But these lock ups aren't just with building. Its everything.

    For example, I hit cmd-Z at one point to undo a deletion, and it literally took 43 seconds before I could type again (again, the beach ball).
  • 0 in reply to Kevin Stallard
    Intellectual 445 points

    One thing is pretty consistent. When I right click a project it is hit or miss whether or not the context menu is going to appear. Sometimes it is 1 to 3 second delay, others, beach ball and then I get the menu.

    I should tell you that I am running a brand new Mac, 10.11.6, SSD hard drive, 16 gigs of RAM

  • 0 in reply to Kevin Stallard
    TI__Guru**** 173310 points

    Kevin,

    We'll take a look at your workspace log to see if it provides any clues. In the meantime, could you also try to get a few stack traces at some different instances where the slowness/lockup is happening? That might provide some additional information. 

    More information on how to get a stack trace is available here: https://wiki.eclipse.org/How_to_report_a_deadlock

     

  • 0
    Expert 1704 points
    I've noticed this happens a lot with active debug sessions. If you stop and restart the debug session, it seems to become more responsive again. It might be leaking.
  • 0 in reply to Kaveh Vaghefi
    TI__Guru**** 171309 points
    Kevin,

    Just adding to Aarti's response, I have been running an active debug session for several hours now on a MacBook Pro with core i5 2.7GHz/8GB but I haven't experienced any memory leaks - it stays around 800~840MB depending on the activities I do.

    I also did not experience any lags, but I don't have as many opened projects in my workspace as you do. Could you try to close a few projects and see if you experience any performance improvement?

    Also, I don't see it in your screenshot, but always pay attention to see if there is a message at the bottom that says "C/C++ Indexer: (xx%)", as it is a performance killer while it is running.

    Hope this helps,
    Rafael
  • 0 in reply to AartiG
    Intellectual 445 points

    Hi Aarti,

    Thanks for taking a look.  When you say "stack traces" keep in mind that I'm not debugging anything.  I guess I should ask, do you mean stack traces from a target debugger view or an Eclipse stack trace?

    If it is an Eclipse stack trace, how do I retrieve this?


    Thanks

    Kevin

  • 0 in reply to AartiG
    Intellectual 445 points
    Yeah, I've been leaving the task window open to see what Eclipse is doing....the Indexer has always been a problem in CDT. I also use QNX's IDE a lot and it has the same issue.

    But so far, I have been seeing a lot of these hangs going on when it doesn't seem that Eclipse is doing anything in the background...
  • 0 in reply to Kevin Stallard
    TI__Guru**** 173310 points

    Kevin Stallard said:
    When you say "stack traces" keep in mind that I'm not debugging anything.  I guess I should ask, do you mean stack traces from a target debugger view or an Eclipse stack trace?

    HI Kevin,

    I was referring to Eclipse stack trace. My previous post had a link that describes how to capture the stack trace.

    Here is the link again: https://wiki.eclipse.org/How_to_report_a_deadlock

    Please paste the contents of the stack trace into a file and then attach the file here. Thanks!

  • 0 in reply to AartiG
    TI__Guru**** 173310 points

    Hi Kevin,

    From your workspace log file it looks like you are working with Perforce version control. Are both your workspace and project files in a perforce controlled directory? If so, one test you could do to see if source control is having an impact on performance is to put the workspace directory just on a regular local directory. Eclipse does a lot of reading/writing into the workspace directory so it will be interesting to see if keeping the workspace local to the machine makes a difference.

    Please let us know if you observe any improvements after you've had a chance to try this.

  • 0 in reply to desouza
    Intellectual 445 points
    In leaving the task window open so I could observe, I'm seeing something that flickers by: "CrashReportJob". It stays there for awhile, nothing else appears to run, and then when it disappears it seems that things start moving again.

    Not sure 100% if I'm seeing this right or if it is related, but its something...
  • 0 in reply to Kevin Stallard
    TI__Genius 9345 points
    Hi Kevin,

    What exact build of CCS are you using? The version is shown in Help > About dialog.
  • 0 in reply to Baltasar Belyavsky
    Intellectual 445 points
    Code Composer Studio

    Version: 6.2.0.00050

    Mac OSX
  • 0 in reply to Kevin Stallard
    TI__Guru**** 173310 points

    Kevin,

    We have a patch that we'd like for you to try out to see if it helps with the lock ups you've been experiencing. The patch is available in this post.

    To install the patch:

    Download the attached file to your machine, and copy it into your <ccs>/ccsv6/eclipse/plugins/ directory.
    Rename the already existing file in that directory, with the same name, to have extension ".jar_orig".
    Rename the downloaded file to have extension ".jar".
    Start (or restart) CCS.

    NOTE: this patch would only work on CCS v6.2.0.00050.

    Could you please give this a try and let us know if it helps with the performance issues?

  • 0 in reply to AartiG
    Expert 1704 points

    Awesome!  I will try it and report back if I run into any issues.  Excited to hear 7.0 is coming out soon too.  I hope this solves these sorts of lockups I've been running into when in an active debug session.

  • 0 in reply to AartiG
    Intellectual 445 points
    Thanks Aarti, I'll give it a try.

    Kevin
  • 0 in reply to AartiG
    Intellectual 445 points
    Hi Aarti,

    This appears to be working much better. It was a bit rough when I first installed it, but since then it seems to be responsive. I'll provide more feedback as time passes. Thanks again.

    Kevin
  • 0 in reply to Kevin Stallard
    TI__Guru**** 173310 points
    Kevin, that is great news. Thanks for the feedback. And do keep us posted if things change as time passes.

    The patch will be included in the CCSv7 release.