Anja von Werden 

A few things do come to mind.

I assume you are well antiquated processing 1000 files?
What I am trying to attain is when did the crashing start?

You were right to move your TMs so its local to your machine as it will absolutely speed up processing.
But so far as the project files are concerned, I understand the source files are on the network but were is the sdlproj and all those sdlxiff files stored?
I trust its also local to your machine?

What is happening at the time of the crash? I assume you are in the Editor View?
Are you trying get results from various resources to apply translations to your segments or is it when you are confirming segments?
When in the editor view, are you performing a virtual merge so all files are open at once?

When you say crash can you describe it? Does Studio close entirely or does it seem "non responsive"?

What do the Studio error logs show when you crash. They can be found here: C:\Users\username\AppData\Roaming\Trados\Trados Studio\Studio17\logs

Lastly do you have any apps installed? 

Lyds

Anja von Werden 

A few things do come to mind.

I assume you are well antiquated processing 1000 files?
What I am trying to attain is when did the crashing start?

You were right to move your TMs so its local to your machine as it will absolutely speed up processing.
But so far as the project files are concerned, I understand the source files are on the network but were is the sdlproj and all those sdlxiff files stored?
I trust its also local to your machine?

What is happening at the time of the crash? I assume you are in the Editor View?
Are you trying get results from various resources to apply translations to your segments or is it when you are confirming segments?
When in the editor view, are you performing a virtual merge so all files are open at once?

When you say crash can you describe it? Does Studio close entirely or does it seem "non responsive"?

What do the Studio error logs show when you crash. They can be found here: C:\Users\username\AppData\Roaming\Trados\Trados Studio\Studio17\logs

Lastly do you have any apps installed? 

Lyds

Hello Lydia,

the crash problem has been occurring for about a year or longer.

However, it's more noticeable the closer I get to the annual delivery deadline as the number of files I have to process increases.

The xliffs and project settings are stored on the network drives (as the local machine does not guarantee secure backups).

Crashes always happen in Editor view. They happen when a single file is open as well as when several merged files are opened. 

Crashes have happened (among others) when I

- deleted a space

- pressed Enter/Return

- confirmed a segment

- in "track changes mode" when the cursor/the marked area covers changed and non-changed text.

Almost all crashes are of the "pooff-and-everything-is-gone" variety. No error message, no frozen screen, the program immediately shuts down and I have to restart it an find all my files again and load them into the editor.

I have no Trados Apps installed (I only used to have the Comment Viewer Plug-in until it stopped working properly and I deleted it)C:\Users\VONA\AppData\Roaming\Trados\Trados

Below find the log file and the error message for a crash WITH message + complete shutdown

Studio\Studio17\logs

Anja von Werden Rather than a screen print, can you please attach the actual log file from Studio.

And can you save the error stack trace you get from 

Hello Lydia,

Can you please advise how to attach the log file? I tried but couldn't find how. As inline text it was rejected as spam and via the "insert" option I could only upload images or videos.

And where do I find the error stack trace ?

Kind regards,

Anja

Anja von Werden when you click Insert and then "Image/video/file - there is an upload option that looks greyed out.
But it will let you select files

And with regards to the stack trace, if you get the error and press the save option it will give you the entire stack trace file

So what I am looking for is:

• Studio log file at time of error/crash
• Error message stack trace - when possible
  
  

Lyds