Hi Ronald,

Unfortunately I don't have an anwer but I would like to join your request. I've been having the same problem and it's getting worse. I think a solution should be provided soon since this is seriously irritating and a waste of time. WE NEED A SOLUTION SOON! I agree with you. I hope they can hear us. 

Regards,

Andrea

Ronald van Riet Andrea Mihajlovic

It's really not enough to post like this and say Studio can't handle large files.  One of the improvements in Studio is the ability to handle larger files than earlier versions and I have tested this with some massive files, considerably larger than 25000 words.

Having said this I'm not discounting that you have a problem. So if you can share files, or explain more how to reproduce the problem then we'll be happy to investigate.

In the meantime please make sure you have updated to the latest build:

SDL Trados Studio 2021 - 16.0.1.2917
SDL MultiTerm 2021 - 16.0.0.158

You can also expect another update in a couple of weeks as we are listening and we are working continuously to ensure the product is working as well as it can.

Dear Paul,

First of all thank you for your quick reply and for working on the issue. This is not to say the team is not working hard.

I have the latest version which I purchased not long ago and that is why I was surprised the Studio just shuts down with no warning. There is nothing more I can tell you about why or how because as I mentioned, there is no warning. My previous version (2019) shut down a few times but not this often. 2021 shuts down just about every 10 minutes now.  I have seen a few comments like this already online so it might be more of a problem than just a few of us. All we are saying is, that this is a problem indeed and since I purchased a brand new product, I think it should be functional and not making my job harder. 

All in all, we are grateful that a team is working on this issue and looking forward to a solution. 

Kind regards,

Andrea

Andrea Mihajlovic

Thank you... can you just check your version however as you have not confirmed you have updated.  The release version is NOT the latest one.  One of the problems that has already been fixed in the initial release was notifications... there are none!  So you won't know that there is an update until you manually apply the one I referred to.  Check your Help -> About to be sure and if you don't have the version I mentioned you can download it from here:

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380

Thank you, Paul for the info. I'll check and follow your advice.

I do have the latest version as you mention, that is thne first thing I check when I want to report a problem.

Please be assured that this is a real and severe problem, costing a lot of productivity and hassle.

I have set the aurosave now to 4 minutes, but that is an interruption that takes a while and happens to ooften. Of course, updates saved in the TM are automatically applied after restarting the project in a fresh copy of Studio, but they are marked as 100% matches and during QA I always filter out the 100% matches, so this screws up my QA. Not filtering them out the QA takes too much time as there are often large numbers of 100% matches and I don't know off hand which I still have to check because of this Studio error.

I got the issue a couple of times too since I installed 2021, not necessarily on large files. Not often, but it happened, while it never did it with previous versions.

Studio just disappears. It does not freeze, does not slow down, does not warn. Just disappears suddenly. No problem to restart it.

Philipee

Hi Ronald van Riet, Andrea Mihajlovic and Philippe Riondel 

If downloading the latest, more stable version as Paul suggested doesn't help (I recommend always being sure to have the latest version), here's a solution that works for me:

I have found that turning off any 'extra' functionality that I don't use prevents these sort of crashes and also speeds Studio up, whatever the version.

For example, when I'm don't need Fragment Matching/Match Repair, I turn it off...

So, here in the Project settings, I do the following:

Or... if you don't work with projects, i.e. 'Translate Single File', turn off the same settings under File>Options

(Individual project settings always overrule the same settings made under File>Options)

I also close the Fragment Matches window in the Editor View if I'm not using it. Most of my work as a proofreader is done in Review mode so I don't often need Fragment matches...

However, if you don't want to turn off Match Repair or Fragment matching, try turning off LookAhead via File>Options, here:

It makes sense to turn off any functionality you don't need/use because it makes software more streamlined, efficient and stable. It works for me, every time!

I hpe this provides you with the solution you need!

All the best,

Ali 

thanks for the tip: I disabled LookAhead and haven't had a single crash all day

Paul: please have your developers look at this apparent link between LookAhead and this problem

Hi Ronald van Riet

I don't think LookAhead, or Fragment matching/Match repair are actually causing the problem. I think it's due to, for example, the size or complexity of the file or other complex content, but that turning off a heavy-duty process that is running unnecessarily frees up more RAM to deal with the complexity of whatever is triggering the problem.

Also, restarting one's system rather than just Studio itself helps prevent heavy-duty software from crashing because it wipes the RAM clean of any background processes that were still running when you closed the system down (even if you've ostensibly closed other programs yourself) so more RAM is available for the software you start up after rebooting your system.

My terminology may not be spot on, I'm not that good at computer jargon but I expect you will see what I mean. Would you agree, Paul?

All the best,

Ali