Hello Vimala Padakanti,
The reason for this misbehavior is most likely caused by a System.OutOfMemoryException, when you try to open a large result file. Please check and let me know, if you experience the same issue, when trying to open results from a small test list execution.
The OutOfMemory exceptions are related to how the Windows OS treats the installed applications and the memory they use from the available RAM. By default the 32-bit executable applications, like Test Studio, have an address space limitation of 2GB put upon the OS. So, even in the cases when the available RAM memory is much more, you can face such exception.
The solution, which you can apply for the computer you use to open the results, is listed as option 3 in this article
along with some further details on the topic how Windows OS handles the applications' memory requests. Basically the idea is to turn on a flag which allows the 32-bit executable to use 3GB memory space block, instead of the default 2GB.
The flag in question is named "LARGEADDRESSAWARE" and should be turned on for few of the executable applications of Test Studio. The instructions advise to turn this on for the Telerik.TestStudio.Desktop.exe
, and I will recommend you perform the same actions for the ArtOfTest.Runner.exe
as well. In case your scenario requires scheduled test list executions, you need to turn on the same flag for the Telerik.TestStudio.Scheduling.Client.exe
on that scheduling server and for the ArtOfTest.Runner.exe
on all execution machines.
Here are some additional points to help you turn on the flag on the required machines.
- To be able to use the editbin command you need a Visual Studio command prompt started with admin privilege and C/C++ Build Tools component installed.
- Then change the directory to the Test Studio installation one - C:\Program Files (x86)\Progress\Test Studio for default installation.
- Execute editbin /LARGEADDRESSAWARE Telerik.TestStudio.Desktop.exe and then the same for the ArtOfTest.Runner.exe.
- Then you can verify if the previous command was successful using dumpbin /headers Telerik.TestStudio.Desktop.exe. We are looking for "Application can handle large (>2GB) addresses" in the "FILE HEADER VALUES".
Once you manage to turn the "LARGEADDRESSAWARE" flag, Test Studio will use 3GB from the memory and hopefully this will improve your experience with loading results from large tests. I would like to assure you, that our engineering team is constantly improving all aspects of the test execution and results in an effort to limit such issues.
I hope that the above suggestion will help you resolve the encountered issue. Please do not hesitate to contact us again, if you need further assistance.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items