• State Suggested Answer
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 303 subscribers
  • Views 3459 views
  • Users 0 members are here
Options
Related

i9 8950K, 32GB Ram but still SDL is crashing multiple times in between work. has it to do with 32 bit vs 64 bit?

Amit Aryan

Dear All, 

As mentioned, I am working on a project with around 60,000 words from English to Marathi. 

But SDL is crashing multiple times per day. I though it might be due to some glitch in my machine. But now I am not using any other software but the SDL is still crashing.

Good news is All the work is saved so the files are safe. I have tried to restart the system but still it continues to crash.

So I read somewhere that a 64 bit software can solve this issue to use all the system resources and capabilities. 

a)Is there any plan for SDL to release that kind of upgrade?
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Amit Aryan said:
    So I read somewhere that a 64 bit software can solve this issue to use all the system resources and capabilities. 

    This is always an interesting topic that we have discussed many times internally. The upshot is that moving to 64-bit is not going to make Studio faster. Moving to 64-bit will allow Studio to use more memory but that doesn’t mean it'll be faster unless we optimise the Studio code too. These optimisations can be obtained while on 32-bit and we are already starting to move certain processing tasks outside of the Studio main processes so that we can have a more performant application. This is the same process that applications such as Chrome and Visual Studio adopted. Having said this there are some situations when processing very large files where 64-bit would indeed be an advantage.

    An interesting thing is to look at what other companies do. Microsoft Office for example still runs on a 32-bit version, and most users prefer this because it's hard to migrate any automation (macros etc.) away from it. This is a very interesting read in that regard: searchenterprisedesktop.techtarget.com/.../Office-32-bit-versus-64-bit In particular the section on the benefits of staying 32-bit. It perhaps gives you some idea of the potential effort involved in moving to 64-bit and also where it may even be more problematic for quite some time.

    Amit Aryan said:
    a)Is there any plan for SDL to release that kind of upgrade?

    Eventually I think this is inevitable but there are no fast track plans to deliver this in the near future, rather we are focusing on where we can make the most improvements in a 32-bit environment for now.

    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

  • 0 in reply to Paul

    Well, comparing Studio with the Office situation is not really correct...

    Studio is in completely different situation than Office - there is simply NOT such a gazzillion of plugins and various other 3rd party components (like GUI controls, etc.) available for Studio as there is for Office.
    And the dependency on those - often legacy, abandoned and without any chance of being resurrected - 32-bit components is the main/only reason to keep Office 32-bit. BTW, the macros automation is not a problem, most of it works as-is in 64-bit Office; there are minor issues like "Long" variable types, but these are easily resolvable by simple macro tweaks.

    Since in Studio SDL completely killed the simple and easy extensibility via COM (as opposed to Office, which still supports COM till today!), this reason is out of question for Studio.

    While the number of Studio apps in the store may seem to be quite high, it's actually nothing compared to the Office addins out there in the world.
    So it wouldn't be such a big problem to convert most of them to 64-bit...
    It would also nicely show how many of them are actually actively maintained (authors would rebuild them) and also actually used (users would demand them)...
Reply
  • 0 in reply to Paul

    Well, comparing Studio with the Office situation is not really correct...

    Studio is in completely different situation than Office - there is simply NOT such a gazzillion of plugins and various other 3rd party components (like GUI controls, etc.) available for Studio as there is for Office.
    And the dependency on those - often legacy, abandoned and without any chance of being resurrected - 32-bit components is the main/only reason to keep Office 32-bit. BTW, the macros automation is not a problem, most of it works as-is in 64-bit Office; there are minor issues like "Long" variable types, but these are easily resolvable by simple macro tweaks.

    Since in Studio SDL completely killed the simple and easy extensibility via COM (as opposed to Office, which still supports COM till today!), this reason is out of question for Studio.

    While the number of Studio apps in the store may seem to be quite high, it's actually nothing compared to the Office addins out there in the world.
    So it wouldn't be such a big problem to convert most of them to 64-bit...
    It would also nicely show how many of them are actually actively maintained (authors would rebuild them) and also actually used (users would demand them)...
Children