Hi Sophie Bedouin

There are 2 similar discussions on the community that might hekp you 

https://community.sdl.com/product-groups/translationproductivity/f/studio/19119/studio-crashes-when-trying-to-open-a-particular-file-in-the-editor

and 

https://community.sdl.com/product-groups/translationproductivity/f/studio/13562/my-studio-2017-sr1-closes-down-without-notice-when-trying-to-analyze-several-large-files

Also if the issue does not appear with any other files added in studio but this one, maybe it is worth to split it in 2 to see if its size is causing this. 

Hope this helps

Best regards, 

Loredana 

Thank you very much, Loredana!

I had already checked the threads you mention without finding an answer to my problem. I did turn off Match reapair etc.

Today I tried dividing the document as you suggested, still no luck.

So far, the only partial solution I have found is creating an unformatted Word source file, translating it to have it in my TM, then repreparing my original source file, and instead of opening it in the editor and having Studio crash, directly creating a target file.

I ran some tests with partial translation and the target Word file I get is fine, most of the segments are translated so I won't have to manually copy-paste too much untranslated content. I'm afraid reviewing against the source in Word will be very time-consuming as I usually do it in the editor, but I don't see any other way right now and I'm on a deadline so I had to do something.

If someone has another suggestion, please feel welcome to share.
Thanks!!

Sophie

When you split the file in 2, did both halved-files crash while preparing them in Trados Studio?

If only one crashed, I'd go on halving the file with problems until you find the culprit, usually an unexpected character… Then correct it and everything should be fine.

When you split the file in 2, did both halved-files crash while preparing them in Trados Studio?

If only one crashed, I'd go on halving the file with problems until you find the culprit, usually an unexpected character… Then correct it and everything should be fine.

Thank you Jesús Prieto!!
It took me quite some time, but I finally isolated the problematic page.

I couldn't find out what was wrong with it though, nothing seems odd, the only text is "Chapter 1" and the graphic content seems identical to the one used for every chapter's frontpage in the document.

Anyway, I just wish SDL would correct this type of bug so Studio directly showed the error and we didn't have to waste so much time.

Thank you all for your help!

Glad you found out what was wrong in the document!

If the source file is corrupted, I may be wrong, but I think that SDL can do very little this time.

Thank you, Jesús!

Re. SDL, what I mean is that shutting down is not an answer. I get that if the file is corrupted, the software is not supposed to be able to work with it, but in my opinion Studio should give an error message identifying the issue (at least: file is corrupted) instead of just crashing and leaving us clueless and frustrated.

I agree with you.

Maybe it's been improved in Trados Studio 2019 or Trados Studio 2021.