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.
