• State Suggested Answer
  • Replies 17 replies
  • Answers 3 answers
  • Subscribers 433 subscribers
  • Views 10781 views
  • Users 0 members are here
Options
Related

Studio 2017 slow to show results in Translation Results window

Bruce Campbell

I am again experiencing waiting times of up to 30 seconds while Studio 2017 spins its wheels searching for matching segments in the Translation Results window.

Needless to say, even a wait of 5 seconds is unacceptably long and I am considering moving back to Studio 2015 (which is luckily still available on my computer).

Could this be due to the new fragment searching in 2017?

(My computer is fast and the files are on an SSD. I just repaired Studio and rebooted my computer a few hours ago.)

Regards,

Bruce Campbell

ASAP Language Services
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Bruce Campbell
    I just set the 3 TMs up for fragment matching again (ReindexTms tool, both "ReIndex" and "UpLift" boxes checked).

    The delays were still occurring when Studio was searching for a match in the TM, so I performed a "Recompute Fuzzy Index Statistics" for all 3 TMs.

    Still encountering long delays in the Translation Results window. (Just had several for around 6-7 seconds, and one for 15 seconds.)

    Well, something is definitely wrong.

    A segment just displayed "Searching..." in the Translation Results window for around 6 MINUTES.

    I decided to translate the segment (still displaying "Searching...") and confirm the translation (Ctrl-Alt-Shift-Enter).

    The error message "The translation unit was not updated (No error detected.)." was displayed in the Translation Results window.

    Studio is still using 25% of my CPU, even though I have now moved on to another segment.

    I decided to restart Studio.

    The next segment showed "Searching..." in the Translation Results window for 3 minutes before I decided to move the cursor to another segment. That stopped the search.

    I just noticed that I do not even have the "TU fragment" box checked in the Translation Memory -> Search dialog.

    Studio just used 60% of my CPU for around 15 seconds while searching for a match. It is still using around 40% of my CPU, even though it is not doing anything.

    I decided to restart Studio, but even though I closed the program it is still running in the background after 5 minutes, still using around 40% of my CPU.

    I presume it is saving my file, so I am a bit reluctant to kill the process. Time to make a tea.

    I have checked back several times, but the process is still running in the background after 25 minutes, still using around 40% of my CPU.

    I decided to restart my computer and start over on the project.

    Regards,
    Bruce Campbell
    ASAP Language Services
  • 0 in reply to Bruce Campbell
    Hi, Bruce - thanks for setting that up and reporting on results. It certainly sounds like something isn't right. It's ... frustrating not having the data to reproduce it. Long shot: is the AnyTM provider involved at all?
    Thanks
    Kevin