You are currently working on UAT 

Studio 2017 crashes

Suddenly after a recent update my Studio 2017 keeps crashing while I'm working on a project. Sometimes there's a warning, sometimes not. 

Parents
  • Hello ,

    Unfortunately this does not give us much data/info to work on.
    Are you able to screen shot the warnings? and post them here in community?

    Often a reason for unexpected crashes is indeed often where ceratin systems are out of date.
    Even out of date graphic drivers will cause Studio to c4rash sometimes.

    Please take a look at the following wiki to trouble shoot unexplained errors and crashes
    community.sdl.com/.../3392.how-to-part-1-trouble-shoot-unexplained-errors-and-unwanted-behavior-in-studiomultiterm

    Please work through both parts of the article and let me know if this helps.

    Oana Nagy | QA Engineer | RWS Group

  • Hi Steven,

    I have been having the same problem, but not as frequently as Diane. I am also running Studio 2017 SR1.

    I have already reverted from Studio 2019 to Studio 2017 SR1 due to problems. Now I am thinking of reverting back to Studio 2017.

    Do you have a link to the install package for Studio 2017 (not SR1), along with a link to the corresponding version of Multiterm?

    With respect to the problem Diane mentions, I have checked the link in your post. Windows is up-to-date. Studio is whitelisted.

    The Studio window just disappeared. Simply closed itself. One second it was there, the next it was gone.

    This probably happens about once a week or less often. It is always a surprise when it happens.

    I was working in Word at the time. I think I moved the cursor from Word back to Studio, but it all happened so fast that I am no longer sure what I did at that final moment.

    Just guessing, but I also recently had a problem with what looked like a memory leak. Studio was running incredibly slowly and when I checked the Task Manager it was using close to 2GB of memory. So I saved my files and exited Studio before it crashed.

    I don't know whether that was the problem this time, as I had been working in Word for a while. But Studio might have been increasing its memory use in the background for half an hour or more before I switched from Word back to Studio.

    Luckily I have not lost any significant amount of work so far, but I would feel safer using Studio 2017 instead of Studio 2017 SR1.

    Best regards,
    Bruce Campbell

Reply
  • Hi Steven,

    I have been having the same problem, but not as frequently as Diane. I am also running Studio 2017 SR1.

    I have already reverted from Studio 2019 to Studio 2017 SR1 due to problems. Now I am thinking of reverting back to Studio 2017.

    Do you have a link to the install package for Studio 2017 (not SR1), along with a link to the corresponding version of Multiterm?

    With respect to the problem Diane mentions, I have checked the link in your post. Windows is up-to-date. Studio is whitelisted.

    The Studio window just disappeared. Simply closed itself. One second it was there, the next it was gone.

    This probably happens about once a week or less often. It is always a surprise when it happens.

    I was working in Word at the time. I think I moved the cursor from Word back to Studio, but it all happened so fast that I am no longer sure what I did at that final moment.

    Just guessing, but I also recently had a problem with what looked like a memory leak. Studio was running incredibly slowly and when I checked the Task Manager it was using close to 2GB of memory. So I saved my files and exited Studio before it crashed.

    I don't know whether that was the problem this time, as I had been working in Word for a while. But Studio might have been increasing its memory use in the background for half an hour or more before I switched from Word back to Studio.

    Luckily I have not lost any significant amount of work so far, but I would feel safer using Studio 2017 instead of Studio 2017 SR1.

    Best regards,
    Bruce Campbell

Children
No Data