Forum: CAT Tools Technical Help
Topic: Trados = 32 or 64 bit application?
Poster: Wendy Cummings
Post title: My problem
[quote]Siegfried Armbruster wrote:
You did get the info you wanted. Now what? What does it mean? I would really be interested what it means to you and how it will influence your potential decisions. [/quote]
A 64 bit compatible application is one that runs in a stable manner on a 64 bit platform such as Win7 64 bit.
A 64 bit application is one that has been compiled as a 64 bit executable, and thus has access to a 64 bit memory space on the operating system
My issue is that the Trados application runs out of memory regularly. This is evidenced by the out of memory exceptions I see on a weekly basis.
I have 8gb of physical ram, which Windows backs with plenty of virtual memory. The issue is not running out of physical memory (as it very rarely is on an OS that utilizes virtual memory).
My current Trados is crashing and it is a 32 bit application. i.e. it has been compiled in 32 bit mode, and has access to a 32 bit memory space. This is evidenced by the fact that when viewed in task manager or another process monitor, it runs natively as a 32 bit app. As a result, regardless of physical memory, the application itself can only reference up to a theoretical 2GB address space, though typically on windows a 32 bit application will fail at around the 1.5GB limit. This again can be seen to happen when monitoring the memory use of Trados and the point at which it becomes unstable.
I wanted to know about the more recent builds of Trados and whether they have been upgraded to an actual 64 bit application, so that they have access to the full address space. This is relevant, as it will hopefully let me discern whether a more modern version of Trados is less likely to crash due to the OOM exceptions that seriously disrupt my workflow.
Clearly it would also be useful to know whether any other modifications to more modern versions of Trados result in higher/lower memory use, specifically as I want to avoid upgrading to a less stable version of the application.
Topic: Trados = 32 or 64 bit application?
Poster: Wendy Cummings
Post title: My problem
[quote]Siegfried Armbruster wrote:
You did get the info you wanted. Now what? What does it mean? I would really be interested what it means to you and how it will influence your potential decisions. [/quote]
A 64 bit compatible application is one that runs in a stable manner on a 64 bit platform such as Win7 64 bit.
A 64 bit application is one that has been compiled as a 64 bit executable, and thus has access to a 64 bit memory space on the operating system
My issue is that the Trados application runs out of memory regularly. This is evidenced by the out of memory exceptions I see on a weekly basis.
I have 8gb of physical ram, which Windows backs with plenty of virtual memory. The issue is not running out of physical memory (as it very rarely is on an OS that utilizes virtual memory).
My current Trados is crashing and it is a 32 bit application. i.e. it has been compiled in 32 bit mode, and has access to a 32 bit memory space. This is evidenced by the fact that when viewed in task manager or another process monitor, it runs natively as a 32 bit app. As a result, regardless of physical memory, the application itself can only reference up to a theoretical 2GB address space, though typically on windows a 32 bit application will fail at around the 1.5GB limit. This again can be seen to happen when monitoring the memory use of Trados and the point at which it becomes unstable.
I wanted to know about the more recent builds of Trados and whether they have been upgraded to an actual 64 bit application, so that they have access to the full address space. This is relevant, as it will hopefully let me discern whether a more modern version of Trados is less likely to crash due to the OOM exceptions that seriously disrupt my workflow.
Clearly it would also be useful to know whether any other modifications to more modern versions of Trados result in higher/lower memory use, specifically as I want to avoid upgrading to a less stable version of the application.