Under Community Review

64-bit version of Studio

Please create a 64-bit version of Studio. At present only a 32-bit version is available, and therefore it can theoretically only access 2-3GB of system memory, meaning that upgrading your machine with more memory then this does not have any beneficial impact on Studio performance.

When handling large files & projects, allowing Studio access to all of your system's memory would make a huge difference in time and performance, and for this the app needs to be 64-bit.

Are there any plans to release a 64-bit version in future?

  • Many other applications that have no particular reason to switch to 64 bits did it.

    Yet, Studio, which often has to handle very big files and has therefore more reasons than most of other applications to do it, did not.
    The lack of usable memory, inherent to 32 bits systems, certainly explains a part of its crashes, such as when it suddenly shuts down in the middle of a sentence... Slow processes (even scrolling sometimes) may also be due to that lack of RAM.

  • Hi Paul,

    Trados crashes with a System.OutOfMemoryException when trying to import a very large XML file (108MB). Trados crashes when it hits 2.5-3 GB of ram usage while adding the file to the project (we can see this with Windows' Task Manager). Moving to 64 bit would obviously solve this problem, as our PCs have a lot of ram installed, which Trados can't currently take advantage of.

    We had to resort to splitting up the XML file in several chunks, which is error-prone and far from ideal.

    So please elevate the priority of moving to 64 bit, as we are experiencing lack of memory-related issues more and more.

    Thanks,

  • I understand and I do appreciate the efforts being made. The comments I have made were entirely in the spirit of constructive criticism to improve a tool which, despite all the competition, still has many assets not matched elsewhere.

  • It is work that has been ongoing and considerable progress has been made.  Unfortunately it's work nobody sees so users understandably get the impression we're doing nothing, but every single release has done something towards it.  There are always competing priorities but the development team are doing their best to deliver on them all and we will get there.

  • I think you have lost the original developers and the current ones are hopelessly overstretched. One gets the impression that they are just poking around in the code to be able to charge money for a new update.