Why does Studio 2017 crash the whole system in Preview mode after coming back from the Editor? Really annoying.

Former Member over 8 years ago

This situation causes the whole SDL Trados Studio 2017 to crash. It loops endlessly through the error message(s) and the only choice is to kill the application with Windows Task Manager. What I am doing? Simply previewing my translation. Once you edit something wrong you noticed in the preview and try to come back to the Preview mode, this is what you get (see attached screenshot below). Please do not ask me about version, etc. Everything is in order and up to date on a powerful Windows 10 Pro system with 8 GB of memory. I have to say that Studio 2017 is buggy, not to mention it gobbles up memory like crazy. 2GB in just a few minutes!!! I have posted other bugs in these fora. I would like real answers AND solutions from the developers team not simple lip service. Thank you.

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Why does Studio 2017 crash the whole system in Preview mode after coming back from the Editor? Really annoying. This situation causes the whole SDL Trados Studio 2017 to crash. It loops endlessly through the error message(s) and the only choice is to kill the application with Windows Task Manager. What I am doing? Simply previewing my translation. Once you edit something wrong you noticed in the preview and try to come back to the Preview mode, this is what you get (see attached screenshot below). Please do not ask me about version, etc. Everything is in order and up to date on a powerful Windows 10 Pro system with 8 GB of memory. I have to say that Studio 2017 is buggy, not to mention it gobbles up memory like crazy. 2GB in just a few minutes!!! I have posted other bugs in these fora. I would like real answers AND solutions from the developers team not simple lip service. Thank you. https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/90/ERROR_5F00_Preview_5F00_in_2D00_HTML.png
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Parents

Paul over 8 years ago

Why don't you log a support case Ozzie if you want this kind of attention? I don't have any problems like this if I go through a similar exercise so this is not going to be a simple thing to answer in here.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Former Member over 8 years ago in reply to Paul

Paul, thanks for your reply. However, I believe there are some systemic issues and I don't think it is a matter of just logging a support case. SDL must address this issue. I know you are very active and really helpful to the SDL community but somebody else should be taking care of this. Denial is not a river in Africa, one of my teachers used to say. Thanks. community.sdl.com/.../42917
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Paul over 8 years ago in reply to Former Member

Ozzie, I don't disagree with you that we have to address any issue that is clearly causing problems. But before we engage the development team on any kind of work the support teams have to qualify the problem as best they can. To do this it's often helpful if they can acquire (and I don't mean the kind that sings in a church) more information from the user to isolate the problem. If they can't isolate it, and if they are seeing consistent complaints from many users then they will engage a developer to look deeper.

I have asked the support team if they are seeing problems of this nature and if we already have something logged for investigation, but it would still make sense for you to log that case as it could be helpful to have a willing user to get to the bottom of where the issue may be coming from if it's not systemic to Studio 2017.

Regards

Paul
aka Ramses, the King of the Nile ;-)

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Former Member over 8 years ago in reply to Paul

Thanks for your quick reply, quips and all, Paul. I know that a sense of humor is always helpful in order not to dramatize a situation beyond of what it is, as long the issue is dealt with and resolved. All right, so I'm going to log a support case. I'll be happy to contribute to the solution with my two cents.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Paul over 8 years ago in reply to Former Member

Hello Ozzie,

This may be related to a bug we have fixed in CU5 which is due for release shortly. Do you have a termbase on your project or do you get these problems without one?

Paul

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Former Member over 8 years ago in reply to Paul

I suppose Studio 2017 is a workhorse, so my translations are loaded with at least 4 TMs and another 4 termbases. I'm also continuously adding and modifying terms, looking for concordances, going back and forth in between translation units. In short, everything a translator will do in a CAT tool. Hey, I'm just taking your great tool to the limit (if that is "the limit" which I doubt). Will that be "the cause" of so many crashes? I don't have any other application in my Windows 10 Pro environment that chocks like this under pressure. Let's hope CU5 brings some relief. Thanks, Paul.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

Former Member over 8 years ago in reply to Paul

I suppose Studio 2017 is a workhorse, so my translations are loaded with at least 4 TMs and another 4 termbases. I'm also continuously adding and modifying terms, looking for concordances, going back and forth in between translation units. In short, everything a translator will do in a CAT tool. Hey, I'm just taking your great tool to the limit (if that is "the limit" which I doubt). Will that be "the cause" of so many crashes? I don't have any other application in my Windows 10 Pro environment that chocks like this under pressure. Let's hope CU5 brings some relief. Thanks, Paul.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

Paul over 8 years ago in reply to Former Member

Let's hope. You might find that deleting all the history from the termbases would resolve this, but probably better to wait for CU5. It's been in beta for the last couple of weeks so hopefully will be a reliable CU.

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Why does Studio 2017 crash the whole system in Preview mode after coming back from the Editor? Really annoying.