• State Suggested Answer
  • Replies 10 replies
  • Answers 5 answers
  • Subscribers 434 subscribers
  • Views 5354 views
  • Users 0 members are here
Options
Related

Studio 2017 frequently crashing

Willem Dubelaar

Good afternoon ladies and gentlemen,

I have just written a longish message, but as I wanted to add tags to it, the message simply disappeared.

My system is Windows 10 Pro 64 bits, fully patched and updated, with Office 365, automatically fully patched and updated. My version of Studio 2017 is also fully patched and updated. I only work locally. I do not do packages and I do not use remote resources.

My antivirus solution is Windows Defender.

Since several months, Studio keeps crsashing frequently during some projects. With ‘frequently’, I mean every five minutes or so. Normally, only the lower, standard Windows error message appears, which says that SDL Trados Studio no longer works for some reason and that a message will be forthcoming after a solution will have been found.

Now, for the first time, the upper of the two messages appeared, which, I hope, your system developers will understand.

I must have reinstalled Studio at least five times of the past several months. I also changes the language of the user interface from English to German, all to no avail.

After each crash, any segment-splitting or segment-merging must be done all over again.

As an aside, I have also noted another, unrelated problem with Studio 2017. It no longer recognises widened or narrowed letter-spacing. In Studio 2015 and earlier, it used to work well. It means that any such spacing must be manually reapplied in the target Word file.

Best regards,

 
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul
    Sorry for the delay in replying, Paul. I did not know that you had responded. I only received a message that I had been mentioned somewhere.
    (In spite of being subscribed to all fora, I only receive a fraction of the postings/responses. Mostly, I only receive a message that something has been moved.)

    Unfortunately, I cannot send you the xml. That particular message has only appeared once and I thought (wrongly) that the message description would be enough.

    Usually, I only receive the lower of the two messages and then have to force-close through the Task Manager, and sometimes the programme simply bails out completely, without warning (that happened early this morning).

    Best regards,
  • 0 in reply to Paul
    Good morning Paul and everyone,

    In my case Studio crashes often when I work with Word files produced by OCR software.

    Would the following details help SDL Gurus find the solution?

    Signature of the problem:
    Problem Event Name: APPCRASH
    Name of the application: SDLTradosStudio. exe. exe
    Application version: 14.1.6329.7
    Time-signature of Application: 59aefecb
    name of the module with error: ntdll. dll. dll
    version of the Module with error: 6.1.7601.23915
    Time-signature of the error module: 59b94a16
    Exception code: c000000374
    Exception shift: 000ce85b
    Operating system version: 6.1.7601.2.1.1.0.0.768.3
    Regional Setup identifier: 1045
  • 0 in reply to Robert Platek
    And this happens over and over. This mystery makes my work like walking on nails.

    Nazwa zdarzenia problemu: APPCRASH
    Nazwa aplikacji: SDLTradosStudio.exe
    Wersja aplikacji: 14.1.6329.7
    Sygnatura czasowa aplikacji: 59aefecb
    Nazwa modułu z błędem: clr.dll
    Wersja modułu z błędem: 4.7.2114.0
    Sygnatura czasowa modułu z błędem: 59a639ae
    Kod wyjątku: c0000005
    Przesunięcie wyjątku: 0001b571
    Wersja systemu operacyjnego: 6.1.7601.2.1.0.768.3
    Identyfikator ustawień regionalnych: 1045
    Dodatkowe informacje 1: 5ae6
    Dodatkowe informacje 2: 5ae673ea10bd070ec6d272121520a1a5
    Dodatkowe informacje 3: 3f1f
    Dodatkowe informacje 4: 3f1fe1d0ca85cff8eb7e3d6acaf48b81
  • 0 in reply to Robert Platek

    Hi Robert,

    Just so I can understand exactly what is going on can you confirm the processes involved.

    "when I work with Word files produced by OCR software"

    What exactly are you doing- and which languages are being affected 

    Scenario 1)

    Are you running the source document through OCR, doing the necessary formatting, then saving the file as docx and importing the docx into Studio and this is where it crashes?

     

    Scenario 2)

    Importing the document directly into Studio and running this through the integrated OCR in Studio?

     

    Kr

    Steve

     

    Oana Nagy | 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

  • 0 in reply to Oana Nagy
    Hello Steve,

    It's #1.

    English to Polish, Polish to English, this happens for both directions. I receive docx files from a translation agency, whose team does the OCR (ABBYY Finereader) and formats the file. I don't have influence on how they do it. But files' layout looks fine. Still, there must be something that eyes can't see and I'm not an expert in Word's nuances.
    Then I import the file into Studio. I translate segment number x, confirm it, and there's a crash. It seems that certain segments cause it. Mostly after restarting the Studio, it doesn't crash again in the same segment. In my current project, the smallest x = 3 :-(

    These crashes do not happen with files that have been written "by hand" or converted from editable PDFs (maybe crashes are thousand times less frequent in the latter case).
  • 0 in reply to Robert Platek

    Hi Robert,

     

    Would you be able to share (next time this happens) the error stack trace please

     

    If you can copy the error into the community, this could help us find the issue (and solution).

    As this only appears to happen occasionally and with files that have been worked on (with ABBYY) I would suggest this is a formatting issue from the clients end, especially as you have no problem with clean editable files.

     

    Kr


    Steve

    Oana Nagy | 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

  • 0 in reply to Oana Nagy

    The system doesn't throw a message like yours. What it does is it pops out and gives choice to shut down the Studio or "look for a solution in Microsoft's resources".

    Yet, this time, still working with OCRed docx, I got this one:

    , which means "The instruction at "#!#!#!#!" referenced memory at "~#~#~#~#". The memory could not be "read".

    I need to point out that I don't have an option to save the stack trace, which makes the problem even more irritating.

    If you find a solution, I will just write translation without confirming, then confirm them every 20th segment, in bulk (changing segment status to 'confirmed').
  • 0 in reply to Robert Platek

    Hi Robert,

    As I dont speak Polish and there is no stack trace i'm hoping maybe  might be able to assist on this one.

    What i think is happening (out on a limb here) is the OCR process is causing the issues for some reason and causing a corruption

    What happens if you re-save the file to simple doc. and not docx?  do you get the same behaviour?

     

    Kr


    Steve

    Oana Nagy | 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