Core trace invoking the wrong instance on second invocation on a different instance of a core

Invoking Trace use cases using the Menu... Tools -> Code Analysis -> (E.g.) Core Trace
does not work for a 2nd invocation on a different instance of the core

E.g. On a device with say 2 R5 instances, let's say A and B

Steps
1 Bring up CCS and run Core trace on say Cortex_R5 instance A
2 Load program etc. collect some trace
3 Close Trace window
4 Switch context to another R5 say instance B 
5 Load program etc. and try to collect trace
6 We notice that a halt on the R5_B does not stop trace recording.
7 The instance that is showing up is for the instance A. If you load a program on A and halt it, will see data show up even though the Core trace the 2nd time was invoked on R5 instance B

 
The key is how the use case was selected
1. Select a core and then from The Menu.. Tools -> Code Analysis -> Core Trace
2. Select a core and then from context menu (Right click), select Code Analysis -> Core Trace

The problem can be observed with method 1

Also using method 1 it works for the 1st instance you try and subsequently all  invocations will be for that instance no matter which instance you try to bring core trace up on. This holds true even if you terminate the debug session and then relaunch debug session for device and try another instance.

The only way you can get it to work for another instance using method 1, is to restart CCS and then go to that other instance. Of course subsequently all invocations will be for this new 1st instance that  you tried once CCS restarted.