• Locked Locked
  • Replies 17 replies
  • Subscribers 56 subscribers
  • Views 5323 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.

"JVM heap low detected" - Problem persists even after changing eclipse and ccstudio configuration files

m r
Prodigy 130 points
Other Parts Discussed in Thread: CCSTUDIO

I have been using CCS Version: 6.0.1.00040 for more than 6 months now. Since past few days I am facing "JVM heap low detected" - Problem. I have applied changes suggested in TI community site for similar problems. I increased Xms and Xmx in both ccstudio and eclipse configuration files as follows:-

 -Xms1024m
-Xmx1024m

I enabled show heap status and can see that 1016 m is available. However  while using CCS this gets filled suddenly and CCS gets stuck with following response.

An internal error occurred during: "Update Monitor".
Java heap space

Please suggest a solution.

  • TI__Guru**** 472341 points
    Hello,
    Can you provide more details on your system? I'm looking for your host OS and specs of your computer (specifically amount of RAM)

    Thanks
    ki
  • in reply to Ki
    Prodigy 130 points

    Hi Ki,

    I am using Code Composer Studio Version: 6.0.1.00040, Windows 7 Professional 2009 Service Pack 1 (64-bit Operating System). 4 GB RAM. As stated earlier I have allocated 1024 MB for the eclipse. While using CCS I can see that heap status remains below 200 for a while and then gradually increases to 1016 and gets stuck. Is this an issue with Garbage collection cycles? Is there a way to increase Garbage collection cycles frequency?

    Thanks,

    m r  

  • in reply to m r
    Prodigy 130 points
    I have posted the question regarding change in Garbage collection cycle frequency in CCS v6 at the link below e2e.ti.com/.../405510
  • in reply to m r
    TI__Guru**** 472341 points
    4 GB RAM should be fine. What are you doing with CCS when you see this warning? Are you in a debug session? If so, what device and connection are you using? What is the size of the project you are working with?

    Thanks
    ki
  • in reply to Ki
    Prodigy 130 points

    I was just editing some code in C source files. The heap gets filled and CCS gets stuck. The entire project size is 1.26MB.

  • in reply to m r
    Expert 1505 points

    I have a similar problem after updating to CCS v6.1  I have enabled the heap indicator, and with 6.0 it almost never hit the max (turns red when it does) with a heap of 512m.  With 6.1 it regularly hits the max when starting a debug session and particularly when starting Tools-> RTOS Analyzer activities. The whole java heap usage seems to have increased with 6.1

    There are 2 things to be set in ccstudio.ini  :
    -Xms40m
    -Xmx512m

    The Xmx is apparently the heap size, what is Xms?  Another post I saw on this subject indicated increasing them together, how are they related?

    Mike

  • in reply to Michael Stich
    TI__Guru**** 472341 points
    Xms is the minimum default heap size. Normally you can leave that alone since the bigger issue is the maximum heap size.

    Some of the RTOS tools can use a lot of heap, especially ROV. I'm not aware of any specific changes in 6.1.0 that would cause a drastic increase in heap usage (and I haven't noticed much of a difference between my 6.0.1 and 6.1.0 installations). If you updated your SYS/BIOS versions or dealing with larger executables, that could have an impact.

    ki
  • in reply to Ki
    Expert 1505 points

    Ok, thanks.  I wouldn't say it is "drastic" increase, maybe 15% to 20%.  I guess I'll just increase it in the ccsstudio.ini file.

    Mike

  • in reply to Michael Stich
    TI__Guru**** 472341 points
    1024 seems to be a good size to increase the max heap size to. Another person was able to resolve their heap issue when upping the max to 1024 (they saw issues when using ROV).

    thanks
    ki
  • in reply to Ki
    Expert 1505 points

    Tried -Xmx1024m and got a pop-up saying it failed to create the java machine.  Backed off to 768 and that worked. Is there another setting that has to go along with this to let it get to 1024?

    Mike

  • in reply to Michael Stich
    TI__Guru**** 472341 points
    What are the specs of your computer (how much RAM do you have)?
  • in reply to Ki
    Expert 1505 points
    Windows 7 Professional, 64 bit, 8 GB ram
  • in reply to Michael Stich
    TI__Guru**** 472341 points
    That is the same specs I have (and I have no problem). Did you also increase -Xms also? Or just -Xmx? And can you try using a new clean workspace folder?
  • in reply to Ki
    TI__Guru**** 472341 points

    Hold on, I just reproduced the issue. What happened was that I had a lot of processes running that used up a lot of RAM and when i tried to run CCS, I guess it noticed that I didn't have much RAM left to compensate for the max heap size and threw up that error. I was a bit surprised because before I launched CCS, I was using just under 6 GB of my 8 GB but I guess there are other factors involved when calculating the available RAM. In any case when I closed some apps and got the usage to about 5 GB, I was able to launch CCS without issue.

  • in reply to Ki
    Expert 1505 points
    Ok, thanks, I'm going to try it at 768 for a while and see how it goes.
    And I did not change the minimum -Xms, left it at 40m
    Mike
  • in reply to Michael Stich
    Prodigy 60 points
    I don't suppose a solution to this was ever found (apart from editing the heap size)?
    I've had to increase mine to 1024 but it still gets stuck and crashes
    I'm using CCS 6.1.0 on a 64-bit Linux Ubuntu 14.04 Virtual Machine (Host of Windows 7) with 4GB RAM allocated for the VM (8 overall on the host),
    I'm not using anything else other than CCS when it crashes, and i'm just editing source code, no debug sessions.
    Any help to try and fix this would be great!
    Thanks :)
    Jenny
  • in reply to Jenny Bosher
    Expert 1505 points

    Seems like each new release of CCS uses more memory to manage ever more features.  I mainly ran into trouble when using the ROV (RTOS Object Viewer) to verify performance in multicore environment.  You would likely do better running CCS natively on windows with the full 8 GB and getting the Virtual Machine out of the way.  I know of no other way than to increase memory somehow, either physically or via increasing the heap size.

    Mike