Hi, Consenso. I'm too having memory leak problems with my Studio 2017 system. I believe it has to do with the way the system handles translation memory and termbases. As a developer, I could tell this is a problem of an inadequate "garbage collection" mechanism. This subject is well explained in this Wikipedia article:
en.wikipedia.org/.../Garbage_collection_(computer_science).
Normally, when translating with Studio 2017 (or previous versions) a lot of database queries are taking place every time you enter into a new target translation unit in addition to the queries triggered by what you're typing. It's a very busy situation, but that is what a CAT tool is supposed to do. However, I believe that the developers should take a better care of garbage collection. I get all sort of error messages and the next thing is that the program becomes unresponsive and then either it crashes by itself or I have to kill it with Windows Task Manager when it goes into an infinite loop. Regarding these memory issues I have posted this:
1) community.sdl.com/.../12209 and
2) community.sdl.com/.../10866
Now, I want to give SDL the benefit of the doubt and think that perhaps if could be a Windows 10 problem, but I'm not sure about that. Other programs, like the entire Office Suite, browsers, etc. never, ever, crash and don't gobble up memory either. I would like SDL to tackle this issue as an actual Studio 2017 problem not as a set of separate 'anecdotes' from some users. Thanks.