Hi all,

We are currently testing the Studio 2017 network version on an external desktop environment. Yesterday one of my colleagues and I were doing a big translation and when my colleague was using Studio 2017, it suddenly crashed. That happened twice. Today, I tried to recreate the same crash, and I think I succeeded. Working on the same files for translation, Studio 2017 crashed three times today.

This translation was a pretty big one, consisting of multiple word-files that were all put together in a Studio package. Most files did not pose a problem, the crashes all occurred when working on the same file. When we're working on translations, we always open all files in the Studio package at once. Of course, we were using upLIFT and our TM was a big one, consisting of around 400,000 TUs. Max. number of hits for concordance search was set at 15 to increase speed.

These are the crash reports:

Crash number 1:

Crash number 2:

Crash number 3:

As you can see, the crashes all seem to be caused by something else. Has anyone else ever seen these errors and are they related to Studio or to Windows (server)? It is odd that this error mainly occurred when working on one file, so the crashes might be related to this particular file. Then again, the last time I tried this particular file did not pose any problems. Could it also be that the TM is simply too large, causing issues? Or it might just be our cloud environment that is causing this issue.

I suspect when my colleague encountered these crashes, Studio was just autosaving, since she also got this additional message when opening the project again:

I think I read on these forums that this last error message is related to closing Studio while it was saving, corrupting the file.

Any help in solving this issue is greatly appreciated! :-)