Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Memory leak on agent machine during browser driven load test

Memory leak on agent machine during browser driven load test

It is important when running a bdlt load test that files which are downloaded or events which occur in the application under test do not trigger other applications to be opened on the agent machine.  For example, opening a pdf report in the application under test will cause the adobe reader process to be launched on the agent machine.  This process is outside of the scope of the browser application so be default SilkPerformer will not attempt to close it.   In time, each user who starts an external process but never closes it again will eventually cause a machine wide memory leak to occur and the load test will fail when the agent runs out of resources.

To prevent this from happening, change the command which triggers the event or alternatively run some code to clean up the processes on the agent machine.

Running taskill to clean up processes left running on an agent.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-04-16 14:30
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.