Trados Studio 2021 gets stuck at given segment during translation

Hello,

I hope you can help me with the following problem that I've stumbled on several times in the past couple of months.
At some point during translation, when going through a certain (previously inoffensive) segment, Trados gets stuck and must be terminated by Task Manager. The segment may be an untranslated segment or a previously translated segment which I'm going through again. It may have format labels or be plain text. I may be a pre-translated segment or a completely virgin one. It doesn't matter: from then on, any attempt to edit the offending segment or even go past it by means of the down arrow key end up in Trados getting stuck.

Usually only a few segments are compromised, meaning I can scroll the editor past the offending block and resume the translation at a later segment.


I've tried many different workarounds:


- Start a new project from scratch with the original Word file and import the TM
- Start a new project from scratch with the sdlxliff file
- Start a new project from a Word file where the offending block has been removed and import the TM, then use the fresh TM/sdlxliff in a further new project with the whole Word file
- Edit the TM to remove the offending block, then start a new project from scratch with the original Word file and import the TM
- Remove all the TM and TB from the project
- Save the .docx Word file in .doc format, then revert it back to .docx and start a new project from scratch
- Manually edit the sdlxliff file in a text editor to remove the offending segments
- Restart Trados

- Restart Windows
- Repair Studio

and a zillion more, including combinations of the above. None seem to work: after a segment initially triggers the bad behaviour, no attempt to finish the translation would work and the project becomes "cursed": the offending block either reappears or shifts down (if the offending segments have been removed from the Word file), However, If start a different project, Trados would work smoothly.

I've found only two solutions so far:
1) either transfer the sdlxliff file on a different computer and resume it from there, or

2) erase all my Trados directory, reinstall Trados and reopen the project.

Needless to say, both Trados (16.1.8.4404) 
and Windows (10) versions are up to date and I apparently have no interference from the antivirus.

I would be endlessly grateful if someone could help me to understand this bug and find a fix.




Parents
  • I apparently have no interference from the antivirus.

    How do you know?  We know that it's no problem on another computer. so that narrows it down to something on your machine.  The most common problem for this sort of issue is your security software:

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

    It might also be related to your resources being on OneDrive or a synched drive somewhere... possibly the result of lookahead even trying to work on recovering a block of segments to memory as you work.  So perhaps try these two things:

    1. copy your TMs to a local folder, and not one that gets synched to anywhere.  Remove your TMs from your project and add them back again from the new location. 
    2. try turning off Lookahead:
      Trados Studio Options window showing Translation Memory settings with 'Enable Lookahead' option highlighted in red indicating a potential issue.

    One of these may help.

    Paul Filkin | 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

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 3:29 AM (GMT 0) on 29 Feb 2024]
  • Hi Paul,

    Thank you for your supersonic answer.

    My folder is local, so no problem on that side.
    As for the antivirus, I checked it with an IT person at some point back in June. I don't remember the details, but I will go through the steps of the link you suggest just in case.

    Anyway, my overall impression is not that something is wrong on my machine, but rather that the software accumulates trash until it overflows. These are the reasons:

    1) The bad behaviour usually happens toward the end of longish projects.
    2) With a freshly started project, the program responds swiftly; as it goes on, it becomes slower; for instance, it may pause a couple of seconds after I hit Ctrl-Enter. The TM results window also starts to lag behind, requiring a few seconds to update or not updating at all until I move to the following segment (that is, segment n+2 wrt to the TM result window).
    3) With a freshly started project, the TB is stable, but as it goes on, it starts to disconnect (and can only be reconnected by restarting the software). This is VERY annoying.

    Just to give you the whole picture, my long projects are in the 20K words range and my TMs in the 1k segment range, so they are still quite small. I run Windows on a Mac via VMware with a 24GB RAM, a configuration which allowed me to happily use Studio 2015 during 5 years without any problems. This said:

    4) I do all my Internet search on Mac and I don't use internet on Windows unless I use an AT engine. In at least two occasions, the problems arose during the final revision of a completed translated project which made no use of AT nor any other internet resource: this implies I was just editing my work locally, so there was nothing to arouse the antivirus suspicion, I think. 

    I will check the antivirus hypothesis and let you know. Thank you again.

  • I can suggest that you use a plugin called TuToTm. It allows you to add individual segments to TMs. You can type the problem segment, source and target, select your active TM and click 'Update TM'. Then, if you have the 'Apply best match after successful lookup' box checked in Options/Editor/Automation, Trados will insert translation into the problem segment and pass it by without focusing on it when you click Ctrl+Enter anywhere before the problem segment.
    I only observed this behavior with GroupShare projects and I am actually not sure if that works for you, but you can try. At least, this is easier than re-installation.

Reply Children