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

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

Thank you, Ali for all the advice. Turning off LookAhead worked for me also. 

Paul, thank you also for advising on the updated version. I was using the updated version, I checked. I'm so glad it works great now.

Hi Andrea Mihajlovic

I'm very pleased that worked for you!

Maybe the more RAM-hungry functions could be turned off as default in the next build... That way, the user's option would be to turn features on rather than off, which seems a little more positive and less likely to cause complaints? Just as certain functionality was removed with the 2019 upgrade to 2021 and replaced with faster apps that can be added as preferred. Is that a sensible idea, Paul??

All the best,

Ali

Alison Field

I also think the default should be off... but this is a product management decision.  Perhaps a good one to raise in the ideas site.

I have set LookAhead off and the problem hasn;t reoccurred, but it apparently stil is a problem in the code somewehere that shoudl be resolved, although my case can be closed now.