• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 436 subscribers
  • Views 465 views
  • Users 0 members are here
Options

Studio 2022 keeps crashing

Seda Yavas

Studio 2022 keeps crashing with the following error message:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

Moved to code block
[edited by: Paul at 10:08 PM (GMT 0) on 26 Mar 2025]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

     

    Apologies for missing this one.  I also moved your almost 3000 lines of logging into a code block so it's easier to work on the forum.

    Can you tell us if you're still experiencing problems after all this time?

    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
  • 0 in reply to Paul

    Hi, Paul. I'm having this exact issue as well...
    I've taken the liberty of including the XML of the Trados error (TM update failed) as well as the log as a code block as well for comparison...
    emoji
  • 0 in reply to Patrick L.

     

    Looking at your error:

    • The crash happens during a TM update, and it escalates from a .NET application exception into a native memory access violation.

    • The inner stack trace references cleanup of layout and control components, which can be fragile if file handles or memory are unexpectedly unavailable - like if OneDrive is moving, syncing, or holding a lock on the TM or project files.

    This is especially suspect if:

    • The *.sdltm file(s) are inside a OneDrive path (e.g. under Documents if your Documents folder is synchronised),

    • Or if the Trados project (.sdlproj) or source/target files are in a OneDrive folder.

    Worth checking if your files are indeed on a OneDrive path.  If they are consider moving them elsewhere or see if you can configure OneDrive to cease synch operations during your working day in these locations.

    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
Reply
  • 0 in reply to Patrick L.

     

    Looking at your error:

    • The crash happens during a TM update, and it escalates from a .NET application exception into a native memory access violation.

    • The inner stack trace references cleanup of layout and control components, which can be fragile if file handles or memory are unexpectedly unavailable - like if OneDrive is moving, syncing, or holding a lock on the TM or project files.

    This is especially suspect if:

    • The *.sdltm file(s) are inside a OneDrive path (e.g. under Documents if your Documents folder is synchronised),

    • Or if the Trados project (.sdlproj) or source/target files are in a OneDrive folder.

    Worth checking if your files are indeed on a OneDrive path.  If they are consider moving them elsewhere or see if you can configure OneDrive to cease synch operations during your working day in these locations.

    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
Children
  • 0 in reply to Paul

    Hi, Paul.

    Thank you for your quick reply. I can confirm that I do not have OneDrive set up on my computer, nor do I have any other kind of active backup service (e.g. Google Drive). Trados Studio's program files and the project files are not being backed up automatically, and I have added an exception in AVG (as suggested in another community post), yet this issue persists. 
    emoji