Memory leaks in SDL Trados Studio 2019 Freelance

Question

I had the memory leak issue with 2017. I recently upgraded from 2015. I thought surely the issue would have been resolved by the 2019 version, so I decided to upgrade again, because Trados has become unusable. Unfortunately, the memory leaks persist. I get the out of memory exception thrown at me constantly. I can't work like this. I quit using cloud-based memories and termbases, but it still happens. What is the deal? I'm not using any extra plugins, but I'd be willing to try disabling any of them that could be causing a problem.

Oana Nagy · Answer

Hi Casey Carmical ,

Can you please advise if you're using the WebLookup plugin? Have you updated it to the latest version 2019?

If so, please try to disable it temporarily and try again without it and see if it works.

Also, please go to Internet Options (in your Internet Explorer)>Security settings. Browse for Scripting>Active scripting: select Disable.

Hope this helps and let me know if it works.

Oana Nagy | RWS Group

_____________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub

Paul · Answer

Hi Casey Carmical 
 
No, weblookup is not part of the Studio installation. You have to download it from the SDL AppStore and install it separately. What specification is your computer?

Paul · Answer

Unknown said: This is such a wrong assumption. I have seen Trados pretty much only degrading in terms of speed, reliability and even functionality (touch scroll support) since 2011. The latest edition is buggy, has serious text input slowdown issues, old bugs unresolved 
 Hi Adrian Komiński 
 It's helpful to be specific so we can address your comments more concretely. There are certainly things we need to fix and quite a bit of work has been implemented under the hood to help us do this. We actively monitor every bug that is thrown in Studio as long as users agree to the customer feedback program when they start Studio. This allows us to identify where the biggest problems are coming from and fix them even if they are not reported to us. 
 Unknown said: ... and STILL hasn't gotten into hi-res interface, despite SDL claiming some months ago they are working on the resolution (no pun intended) to this problem. 
 This unfortunately still a work in progress with many parts of the application behving correctly and others not. It didn't progress as quickly as we would have liked so you are correct in that we still don't provide 100% support for hi-res screens. 
 Unknown said: 2019 vs 2017 in my eyes is only the fancy and useless "Tell me something" bar and the new project creation window. While promising, I found myself having to go to the next steps anyway - often for stuff like enabling the merging of segments, etc. 
 It is a bit more than this, but another important point to note is that we also track the things people are searching for and if we see no results are being returned then we will enhance this with each CU... also courtesy of the customer feedback program in the application. At the moment I think it does peretty well for new users, but I would agree that there are many things a more sophisticated user might want to look for and it won't be found. But keep using it and we'll be able to refine this positively over time.

Paul · Answer

Hi Casey Carmical 
 
In this case I think we need to help find out what's causing this in your environment because if this was happenning generally we would certainly know about it. How long does it take for you to be able to see these crashes? Can you deliberately cause it? These things will make it easy for you to reproduce it and then send me the Studio logs so we can see what might be causing this. 
 
You can find the logs here: 
 
File -> View Log file 
 
Reproduce the issue and once it happens restart Studio and save the log. Then send it to me at pfilkin@sdl.com (use dropbox or similar if they are too large to email)

Paul · Answer

Hi Casey Carmical 
 
Thank you for sending me the log file. The development team looked at this for me and believe this to be a fairly 'classic' Out Of Memory message occurring during saving a file - hence all the references to filter framework, SDLXLIFF etc. But what's always tricky is that this might just be the end result of an Out Of Memory issue bubbling up slowly but surely and then ultimately leading to not being able to save the file. 
 
Can you tell me if you leave Studio running for long periods of time or if you close it every day after working? We checked the telemetry logs we get when errors appear and since Studio 2019 has been released the Out Of Memory problem has only occurred 16 times across our entire userbase so I don't think this is a common issue.

Trados Studio > 1. Trados Studio

Memory leaks in SDL Trados Studio 2019 Freelance