• Replies 8 replies
  • Subscribers 431 subscribers
  • Views 3580 views
  • Users 0 members are here
Options
Related

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

Former Member
Former Member

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.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 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

  • Former Member
    Former Member 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
  • 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

Reply
  • 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

Children