• State Suggested Answer
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 434 subscribers
  • Views 1805 views
  • Users 0 members are here
Options
Related

Both Studio and MultiTerm 2017 use up 100% of disk space when opening and after a few hours of use.

Akke Wagenaar

While I still have loads of diskspace free. I am on Windows 10 computer.

My termbase is very large. Whether I open a small or large file in Studio, after a while the disk space used is 100%.

First I thought it was Chrome or Firefox, but it's actually Studio and/or MultiTerm.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Lydia Simplicio
    Hello Steven,

    Thanks for your quick answer.

    This started one month ago when (I think) I had the latest update.
    I changed from Chrome to Firefox and nothing changed at that time.

    I do not have Web lookup app installed.
    Someone mentioned on the other posting 13344 that the cause might be Linguee. I have that open all the time, always on 3 or 4 different tabs. So I will try that out and open a second laptop on the side to open Chrome/Firefox.

    Anyway, the latest update some days ago (maybe it was older but I was offline for 2 weeks) did not install correctly and I had to repair Studio and then disk use really got out of hand.

    I will keep you posted. Because I am now working on a large projects, I cannot have any problems with Studio.
    I will try the different solutions next week and keep you updated.

    BR
  • 0 in reply to Akke Wagenaar

    I have a similar issue, however it is when looking up my TM (1GB). I think it might be a memory leak. I do not use WebLookup, Studio runs on Parallels and my Chrome is open in MacOs.

    I have also tried to deactivate Active components in Explorer but then my computer started behaving in a very odd way, like flashing the screen and other weird stuff.

    Taskmgr.exe says that Studio takes up 300MB of memory (54%). I do not notice any particular spike (+20MB) when Studio is greyed out and I have to wait 10 seconds for it to move to the next segment. It is almost impossible to work with my TM. I often have to deactivate it!
  • 0 in reply to Paola

    Hello

    Although we cannot offer direct support for MAC users - An installation of Studio via Parallels works without issue for the vast majority of users.

    However I notice you mentioned that Studio was taking up over 50%! of the memory (300MB), which suggests that you have not assigned enough RAM to the Parallels installation.

    This indeed would explain the sluggish performance and freezes you are experiencing and is easily rectified.

    As an absolute minimum- we would recommend at least 4GB RAM-

    You can assign more RAM to Parallels very quickly and easily-

    I am quite positive that once you have assigned enough RAM, you will see a much faster and smoother performance.

    Also your TM is starting to nudge towards the larger than average size for a local TM (as opposed to server based).

    Naturally the larger the TM- the longer the search is going to take, so the following options will also speed up the search

    1) Try 'reindexing' the TM

    2) Remove any data that is outdated or that you no longer need or use (TM Maintenance)-

    https://www.sdltrados.com/video/translators-talk-trados-translation-memory-maintenance/114529/

     

    Please let me know how you get on.

    Lydia Simplicio | 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

  • 0 in reply to Lydia Simplicio
    Hello Steven Whale,
    I have done a test, first in the morning only working in Studio, nothing else. Disk use stayed very low for hours. Then I opened Multiterm and a termbase, and disk use stayed low. Then a few hours later, I opened Firefox with only 1 tab open, and disk use stayed low. After some hours, I opened some more tabs. Disk use went up a bit, but slowly, at the end of the day, it had become 100%. So Firefox is the culprit (and/or Linguee) and I guess the only solution is to open only a few tabs until Firefox (and Chrome!) realize that they are causing users problems.