Hi Jan,

I have done a little research on this and it appears this happens when there is a memory leak  and the 'Lsass.exe' is repeating commands over and over where it should not be.  Or indeed there may be a bug that is replicating the 'Lsass.exe' that requires removing.

Please take a look at the these resolution(s)  from Microsoft and let me know if any of the suggestions resolve the issue.

Kr

Steve

Hello Steven,

I checked the mentioned resolutions and upgraded my network device drivers to the latest versions. However, the problem persists. Intersting: when I disable the client (server) termbanks, everything runs smoothly. I am getting a bit desperate because it seems impossible to use client termbanks.

Jan

UPDATE: I opened the same package in Studio 2015, using the same settings and termbanks. Guess what: no problems at all, cpu utilisation max. 3 %, low memory usage! So, this might be a bug in Studio 2017. For now, i will finish this project in Studio 2015, lacking some the new productivity features. I hope you will be able to have a closer look at this and am looking forward for any findings. 

Cheers

Jan

Hello Steven,

I checked the mentioned resolutions and upgraded my network device drivers to the latest versions. However, the problem persists. Intersting: when I disable the client (server) termbanks, everything runs smoothly. I am getting a bit desperate because it seems impossible to use client termbanks.

Jan

UPDATE: I opened the same package in Studio 2015, using the same settings and termbanks. Guess what: no problems at all, cpu utilisation max. 3 %, low memory usage! So, this might be a bug in Studio 2017. For now, i will finish this project in Studio 2015, lacking some the new productivity features. I hope you will be able to have a closer look at this and am looking forward for any findings. 

Cheers

Jan

Hi Steve, the tech team answered me today as following below.

Best Regards, Jan

Hello Jan,

This is a Studio defect ( LTB-1649) that has been reported top our dev team in order to be fixed in future releases.

As workaround to this issue you can still use Studio 2015 or "Clean" the termbase by removing all the history of the terms in an exported XML but this will lose the history of the terms.

Please let me know if there is anything else that I can help you with.

Please ensure that the case number remains in the subject at all times when sending any related correspondence.

Kind regards,

SDL Support

Any news on that? Happens here too and renders Studio unusable after a while. A resolution is needed asap, really...