Addition: Sometimes Trados does not close but it is impossible to get rid of the same error report. Which means that I have to close Trados myself.

Hi Mats Linder

I have a group of things that I do if Studio is slow or crashes. Even if you have no speed or stability problems normally, they can happen with a big/old/complex/multi-file project. Here's what works for me:

1) Go to File > Options > Editor > Automation then UNtick 'Enable LookAhead' under 'Translation Memory' and UNtick 'Enable verification of segment' under 'After Confirming Segments Manually'

Both these options should help speed things up. You can then verify the file after you've finished working on it all in one go via the Review tab > Verify or by clicking F8.

Then, in the Project Settings (or via File>Options if you create your own projects or work via Translate Single File), turn OFF upLift Match Repair:

Turning this setting off seems to help with files that for some reason cause Studio to crash. I am sure it helps with speed too.

If you want to know what any setting means under File > Options or under Project Settings, click the Help button bottom right of the settings window:

Keeping these settings turned on if you need them works fine if you have a hi-spec fast computer and an excellent broadband connection. However, in less than perfect scenarios, it can help to turn one or all of them off.

I always have them all turned off unless I need them, and Studio works well for me...

I hope this helps,

All the best,

Ali

Hi Mats Linder

I have a group of things that I do if Studio is slow or crashes. Even if you have no speed or stability problems normally, they can happen with a big/old/complex/multi-file project. Here's what works for me:

1) Go to File > Options > Editor > Automation then UNtick 'Enable LookAhead' under 'Translation Memory' and UNtick 'Enable verification of segment' under 'After Confirming Segments Manually'

Both these options should help speed things up. You can then verify the file after you've finished working on it all in one go via the Review tab > Verify or by clicking F8.

Then, in the Project Settings (or via File>Options if you create your own projects or work via Translate Single File), turn OFF upLift Match Repair:

Turning this setting off seems to help with files that for some reason cause Studio to crash. I am sure it helps with speed too.

If you want to know what any setting means under File > Options or under Project Settings, click the Help button bottom right of the settings window:

Keeping these settings turned on if you need them works fine if you have a hi-spec fast computer and an excellent broadband connection. However, in less than perfect scenarios, it can help to turn one or all of them off.

I always have them all turned off unless I need them, and Studio works well for me...

I hope this helps,

All the best,

Ali

Hi Alison

Thanks for your suggestions! I have to admit that I was sceptical, since they all seemed to affect the speed of the program and the computer, whereas my problem seemed to be something completely different. However: so far it has worked! It's like a miracle. Thanks again!

I think that RWS should investigate the fact that one or more of these settings may cause a problem like mine. I doubt that it is unique. For instance, verification of segment may be a useful feature. (I shall try activating that again and see what happens.)

Best regards,

Mats

Mats Linder

Hi Mats,

I am positive that none of these settings cause the problem, but that they free up enough RAM to enable the software to deal with whatever really is causing the problem.

RWS and SDL before them have been trying to find the cause of problems such as this but the biggest problem is that the Windows 'Object Reference' error can be triggered by so many different things that the solutions are also many and varied and not always directly triggered by Studio or by the same functionality of Studio combined with the other software present on a system.

Re-enabling one process at a time should show you which needs to be turned off to avoid triggering the problem even though (as I said) the process itself may not be the actual trigger but could help Studio run efficiently by being turned off.

All the best!

Ali

Hi Alison,

Thank you for this further information. I suspected that it is a problem with Windows in connection with Trados and thus difficult to come to grips with... Anyway, it is now rearing its head again, although not at all as often (but just as random).

Best,

Mats