• State Suggested Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 5370 views
  • Users 0 members are here
Options
Related

SDL Trados Studio 2017 keeps crashing on me. Error: "Cannot validate SDL plug-in" in SDL.Desktop.Platform.dll

Former Member
Former Member

Running under Windows 10 Pro, Version 1607, Build 14393.953, 8GB RAM. Question: could it be because of Visual Studio 2017 (installed a few weeks ago)? With Visual Studio 2015 installed I had no problems.

Thanks.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Did you start Trados Studio 2017 within the last few weeks of installing VS 2017? I'd try a reset, and a repair installation first and see if this helps.

    Regards

    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

  • Former Member
    0 Former Member in reply to Paul

    Paul, the "repair" process did not work, not even a complete reinstallation of Studio 2017. Before and now the program crashes and one common error is "Out of Memory Exception (was thrown)." I'm running version 14.0.5821.4. Studio 2017 seems to be very memory-hungry. For instance, in my computer, with 8GB of memory, it gobbles up more than 2GB, almost 3G, of memory and then crashes. Some "garbage collection" is in order by the developers. In general, Studio first reports this "out of memory" warning or error, only to crash the next moment. In addition, should I decide to debug the failing application, it keeps asking me for a "New Instance of Microsoft Visual Studio 2015". This makes me assume that the last compilation of Studio 2017 was done with VS 2015. Incidentally, as I mentioned it before, I have installed VS 2017. What do the developers have to say about all these issues? Their input is appreciated. [A curious note here: the last time Studio 2017 crashed, there was 2.1 GB of memory left, out of 4,2 GB at the moment of restarting Studio 2017].

    Thanks.

     

     
Reply
  • Former Member
    0 Former Member in reply to Paul

    Paul, the "repair" process did not work, not even a complete reinstallation of Studio 2017. Before and now the program crashes and one common error is "Out of Memory Exception (was thrown)." I'm running version 14.0.5821.4. Studio 2017 seems to be very memory-hungry. For instance, in my computer, with 8GB of memory, it gobbles up more than 2GB, almost 3G, of memory and then crashes. Some "garbage collection" is in order by the developers. In general, Studio first reports this "out of memory" warning or error, only to crash the next moment. In addition, should I decide to debug the failing application, it keeps asking me for a "New Instance of Microsoft Visual Studio 2015". This makes me assume that the last compilation of Studio 2017 was done with VS 2015. Incidentally, as I mentioned it before, I have installed VS 2017. What do the developers have to say about all these issues? Their input is appreciated. [A curious note here: the last time Studio 2017 crashed, there was 2.1 GB of memory left, out of 4,2 GB at the moment of restarting Studio 2017].

    Thanks.

     

     
Children