UFT System.OutOfMemoryException error

  • Questions
  • UFT System.OutOfMemoryException error
Question ID: 107001
1
0

Some of our offshore users are running large amounts of batch jobs in the evening exceeding 30 scripts. They are running on machines with 32GB of Ram and i5 or i7 processors. While running, UFT is dieing in the middle of their executions. This error message was found in the system logs from when it stopped at one point

Application: UFT.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an internal error in the .NET Runtime at IP 7251BB1D (72390000) with exit code 80131506.

Also in the console window they get a system.outofmemoryexception and are reporting the worker process is tapping out the 32GB of memory on the machines. I have asked that they go back into their scripts and look at savings they could get by doing garbage cleanup programmatically. They have also asked that we change the .net framework on the machine to do more garbage collection. Is this something you all would think is a way to approach this issue? Do you all have any suggestions on how we can overcome this issue?

Marked as spam
Posted by (Questions: 359, Answers: 26)
Asked on July 29, 2016 2:44 pm
38 views
Answers (1)
1
Private answer

Yes, when running a .NET application under test, using the .NET framework mechanism to automatically invoke garbage collection is recommended. In addition, here are some other considerations:

1) Make sure your UFT host machine(s) are on the latest patch for their version (e.g., UFT 12.02 Patch 5).

2) Restarting UFT between test runs will help flush memory. You can accomplish this by opening the UFT host machine's Remote Agent settings, then look under the Cleanup section (Restart testing tool after runs). To open the Remote Agent settings, right-click the icon in the Windows System Tray.

3) It is good practice to break up your tests into smaller batches/test sets and kick them off separately from ALM/QC at different times.

4) For more best practices related to memory, please reference this HP KB:

https://softwaresupport.hpe.com/group/softwaresupport/search-result/-/facetsearch/document/KM197527

Marked as spam
Posted by (Questions: 0, Answers: 707)
Answered on July 29, 2016 2:45 pm
Great info! Thanks!!
( at July 29, 2016 2:45 pm)