CCSv6 Hangs When Copying a Particular Project

Indeed, it hangs this way on other projects as well.

If my moving of my workspace was the cause of the problem, it would REALLY be helpful to know the proper way to move a workspace to a different directory.

One other point that seems relevant:  if I KILL the process   ccstudio.exe   then I get the Blue Screen of Death.  But if I just shut down my system, it appears CCS DOES respond to that by exiting gracefully, even thought it does not respond to any user input.

Kind regards,
Vic

Victor,

Victor Wheeler said:

I did this by setting CCS to prompt on every launch for the workspace, then shutting down CCS, then moving the workspace from:

E:\Dev\Clients\HM\Dash_2\fw\

to

E:\Dev\Clients\HM\Dash_2\fw\02LrnTI\

And then re-launched CCS and when it prompted for the workspace, I directed it to the new directory, and there SEEMED to be no problems.

I tried following a similar procedure with one of my workspaces, then did a copy/paste of a couple of projects and could not reproduce the problem. I also imported your project into the workspace and was able to copy/paste it successfully. 

Can you zip up the .metadata folder from your workspace and attach it here? We could take a look at it to see if anything stands out.

In the meantime, rather than moving the workspace, could you try opening a new workspace in the desired directory (using CCS menu File->Switch Workspace->Other, and specify the new directory), then importing all the projects into the new workspace, and check if the copy/paste still triggers the same problem?

Hello!

I think it is a problem with the actual routine that does "Reporting encoding changes".  Here's why:

1.  I have mixed files in this project:  at least the .S file uses CR/LF pairs for line endings, whereas most, if not all other files use only LF.

2.  I created the new workspace (on an empty folder) as you suggested and imported the project (07_LEDBlink_SK_Timer) and it imported and built without any errors.  Then I cleaned the project to reduce copy overhead, and then...

3.  I did a COPY of the project in Project Explorer, and then a PASTE, and it gets to the same point and hangs, again with the "Reporting encoding changes" status message.

The following is a screenshot showing the new directory created and a comparison of the files.  You can see that some source files have been copied and others not, and I believe it is in this process that something (a file encoded differently?) is triggering the "job" "Reporting encoding changes", and then, according to the bits of some of the Eclipse bugs I read, one thread takes over and nothing else will happen until that thread completes, and it doesn't complete!  I have tried letting run for as long as an hour now.  I'm going to do the same on the new workspace to see if it will actually finish.  But whatever this "job" is that it is trying to do, it is ... hmmm...  shall I say it?  an engineering disaster, and appears, according to the bugs I read, to have been around since 2005.  Most of the bug reports end off (get closed) with "unable to replicate"!  Do a Google search on the QUOTED string "Reporting encoding changes" and read the Eclipse bugs found and see if you concur.

Meanwhile, here the screenshot showing the file DIFF:

And as requested, here is a .ZIP file containing the original .metadata folder.  (Sorry, when I clicked POST it would not allow this 26MB file.)   However, since it is doing it on new workspace (with just this ONE project imported into it), here's is the .metadata folder of the new workspace.

02LrnTI.metadata.zip

Thoughts?

After I get my computer rebooted, I will send a copy of the ENTIRE new work so you can do a file comparison, in case it contains any clues.

Kind regards,
Vic

As promised, here is the entire (new, and cleaned) workspace.  The imported project ("07_...") was imported from the original workspace, and builds without errors.  I tried copying it to the same workspace with the new name  "08_...Hal",  and and it hung again at exactly the same place.

Here is the ENTIRE workspace in case it contains more clues.  The "08_...Hal" project does not show up in the CCS Project Explorer (the copy never completed), but the partially-copied directory is there.

02LrnTI.zip

For the record, I converted the .S file  and  test.cmd   to have Unix line endings, and tried the copy again, and it STILL hangs in exactly the same place. So those 2 files were not the trigger. Big question: what triggers the "Reporting encoding changes" job?

Victor,

We will take a look at the workspace logs. Can you confirm one more thing? If you import the project to a new workspace and do the copy/paste immediately, ie before building the project, does it still hang?

Victor,

I am consulting with some engineers and they think it might be helpful if we can get the java call stack dump when CCS is hung. Maybe 2 or 3 log captures within a 30-40 second time frame might indicate if we are consistently stuck in the same thread. Would you be able to capture this and send to us?

To get a java call stack, you can use jstack command line tool that is part of the JDK. If you do not have JDK installed you would need to download and install it.

After installing JDK, the command:
jstack -l CCSTudioProcessID
should generate the call stack dump to standard output.

If things are truly stuck then –F option may be necessary. 

Below is the help for jstack.

===================

C:\Program Files (x86)\Java\jdk1.7.0_60\bin>jstack

Usage:

    jstack [-l] <pid>

        (to connect to running process)

    jstack -F [-m] [-l] <pid>

        (to connect to a hung process)

    jstack [-m] [-l] <executable> <core>

        (to connect to a core file)

    jstack [-m] [-l] [server_id@]<remote server IP or hostname>

        (to connect to a remote debug server)

Options:

    -F  to force a thread dump. Use when jstack <pid> does not respond (process is hung)
   -m  to print both java and native frames (mixed mode)
   -l  long listing. Prints additional information about locks
   -h or -help to print this help message

=====================

20160420_1423xx_java_stack_dumps.zip

Certainly!

I got you 5 stack dumps at 10-second intervals.  The filenames indicate the time the stack dumps were taken (YYYYMMDD_HHMMSS_....txt).

Attached is a .ZIP file that contains all 5.

Hoping this helps lead to the problem,
Vic

Hi Victor,

We were able to reproduce the problem, and know the root cause of it.  This is a bug in Eclipse.  It is the same bug as the one reported in https://bugs.eclipse.org/bugs//show_bug.cgi?id=339859.  I will try to implement a workaround for it for CCS v6.2.0.  I have opened a Jira entry to track this issue: https://jira.itg.ti.com/browse/CCDSK-469.  

This problem affects any project that has linked files/folders relative to any path-variable.  You can see all the path-variables for a project in the Properties > Resource > Linked Resources dialog page, on the Path Variables tab.  The same page also shows all the linked resources on the Linked Resources tab.

The only workaround i can think of right now is for you to manually copy the project using an external tool, like Windows Explorer.  Once you've made the copy in the filesystem, you'll need to also edit the .project file to adjust the <name> element to reflect the new project name.

- Baltasar

Hello, Baltasar!

"Root cause" is music to my ears!!

It alarms me however, that this bug appears to be unhandled for the last 5 years.  Am I reading that right?

Does TI have anyone on the Eclipse team that might be able to address it at its source?

Kind regards,
Vic

Thank you, Baltasar!

It's VERY good to know this is destined to be fixed.

One thing:  my DNS doesn't find an IP addres for  jira.itg.ti.com  .  I'm guessing TI network has a private DNS server that serves that IP address.  True?

Kind regards,
Vic

Outstanding!!!  :-)