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.

CCSv4 Launch crashes with => JVM terminated. Exit Code = 1 or JVM terminated. Exit Code = -1073741819 on different systems

One of our customer are facing the issues with CCSV4 simulator launchingh.

Reg the crash: Open CCS.
From Target Menu -> select TI Debugger.
When we try the above step, CCS crashes with the error (sent in earlier mail as snapshot).

They browsed regarding the error and I think it is related to the microsoft. We did not see this error on one of the laptop. 

The pop up shows the following error -
JVM terminated. Exit Code = 1 in some PCs and
JVM terminated. Exit Code = -1073741819 with the message "javaw has encountered a problem. Sorry for the inconvenience" and in some other PCs
 
Is this crash due to some incompatibility between eclipse and javaw version?
 
1) Can you please give us some inputs on which Javaw version should be used?
 
2) How can we find the current javaw version on our PCs?
 
3) This error occurs with both licensed and unlicensed versions. We tried with CCS version 4.1.0 (downloaded from the TI wiki link)
    What could be the reason for this error?

Looking forward to your response.

Best regards,
Vedananda Gowd.R

  • Hi,

    The JVM error does not necessarily mean the issue is with the JVM itself. It could mean many things. Could you have the customer send a crash dump file? See #6 of: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx

    Thanks

    ki

  •  

    Thank you for the reply and information.

    They have used an installer (.exe). And this do not have a CC folder (This is seen in CCS version 3.3)
    In CCS 4, they are not able to see logs folder also.-> searched for .dmp file. And this was also not available.
     
    Is there any other way we can collect the dump file ?
    Thanks and regards,
    Vedananda Gowd.R
     
  • yes, the cc folder was only in 3.3. The dump files in v4 are found: "For CCSv4 users, the mini-dump files are located in a different path: <INSTALL DIR>\ccsv4\DebugServer\win32\components\Log"

    In addition to providing a dmp file (if one exists), could you also provide more details (basically #2 - #5).

    Thanks

    ki

  • Hi Ki,

     

    Thanks for your reply. I have solved this problem by changing the stack size into 0x10000. Hence, the crash may caused by the stack overflowing.

     

    Regards

     

    Chengwei

  • Good to hear. Thanks for letting us know.

    ki

  • Just intalled CCS v4. Having similar problem when trying to launch selected configuration. How do I change the stack size?

    J

  • You can set it in the build properties (right click on project, select Build properties, select C/C++ Build in the left pane, in the Tool Settings tab, go under C6000 Linker and select the Basic Options node. In there you will see options to specify stack size)

    Thanks

    ki

  • hi ki,

    Ihave changed my stack size to 0x400,but still my ccs is crashing down.

    if my stack size is 0x400 ,there is no error ccs is shuttind down.

    if i am changing the stack size to more i.e ox500,it is displaying the error as

    "run placement fall for object".stack",size 0x500.Available ranges:RAMM1 size: 0x400 unused:0x400 max hole: 0x400"

    CCS Version :4.1.2.00027

    Debug tool :XDS100V2