Many CA Plex users are receiving an 'out of memory' error or GPF. We have been waiting for either a memory leak fix OR a 64-bit version of CA Plex.exe.
This article explains the benefits of 64-bit hardware for Plex.exe, and how to get there with just a few steps
CMFirst opened Case 00699969, CA will consider this option embedded in the product in the future.
In the short term, CA is fine with the followings:
- It is ok from CA’s point if Plex users use “Editbin.exe /LARGEADDRESSAWARE Plex.exe” to modify the binary at own risk.
- If any problems occur, and the same problem occurred pre-modified version, it will be supported.
In addition, CA will appreciate if we as a user report problems due to this modification; since it will help CA's QA time.
Simply execute following command against Plex.exe
"%PathToEditbin.exe%/Editbin.exe" /LARGEADDRESSAWARE "%PathToPlex.exe%\Plex.exe"
You find Editbin.exe under "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin"
%PathToPlex.exe% "C:\Program Files (x86)\CA\Plex\n.n or your Plex install directory.
Where n.n is 7.1 or 7.0.
Real world benefit examples:
- Working with 1GB local model changing many Panel layouts. When we tried to update the changes to the Group Model, CA Plex generated GPF without the 64-bit option. However, with the 64-bit option it updated without any issues. The benefit for this case is that all the work didn’t get lost.
- Generation performance, CA Plex slowed down drastically generating sources when the memory usage (from Task Manager) is near 1.8 or 1.9 GB, due to 2GB is a limit of 32-bit application. However, with the 64-bit option, CA Plex does not slow down and consumes over 2GB of memory.
- CA Plex can generate more functions without crashing.
This isn't a memory leak fix. It is only giving a longer life to the Plex.exe. We haven't observed yet, but in theory it will crash if it consumes near 4GB of memory.
The threat here, is that the loss of your work could be larger if you don't save the local model often.