[Richard]

I've had this issue previously with Mxed before from memory and noticing it a lot with Fire - in this case when I have launched a test direct to Fire from the plugin (SU), Fire runs brilliantly though stopping it is another matter. Unlike under Production where MR stops fairly quickly the Fire Engine seems to wait till it has reached a next sampling level - in cases some time!

As these are tests I may just close them out - however if one does close it out prior to it stopping (often a while as mentioned) it seems (could be wrong) it continues to run yet task manager shows it as not running and yet also my CPU fan is raging much like it did at launch!

Could well be my imagination!