QTP long run
I'm running a QTP test on a remote machine that checks our web applicatiion (on i.e. 9) and suppose to find a memory leak in the browser.
The script runs perfectly for about 12 hours. Then, according to the log that i've created in the script, QTP fails to recognize some of the objects.
And after several hours it doesn't recognize any of the objects.
It's very strange since it DOES run the script correctly for 12 hours and for some reason it fails afterwards.
QTP version is 11 and i installed the patch for the ie 9 (QTPWEB_00078).
The remote machine is opened using vmware client, but the problem occurs also when running the test using Remote Desktop.
Another thing - in the past, when i tried to run the test, i got "ntdll.dll" error. So i've done some coding changes to prevent memory leak from the QTP side and also i run the test
in fast mode. So currently the test is running in fast mode and the ntdll.dll error doesn't occur.
Can anyone please help me?
You are not the first one to experience this. I also had similar issues but that was with likes of QTP 10 or so. Our script needed a 2-3 day of window for full run and QTP use to hang after 15-20 odd hrs. We finally used some workarounds, The scripts use to save progress after every 20 iterations. Then after every 150 odd iterations we used to restart QTP by executing a external script which closes QTP, kills explorer.exe and relaunch explorer and QTP. Killing explorer.exe used to help recover some memory space
Thanks for your reply.
The thing is that we need to follow the size of memory leak of the iexplore process bcz the script checks a memory leak of the browser.
That's why i can't close the iexplore process.
You're probably better off using something like Drip to test for memory leaks.
QTP itself has a history of memory leak problems.
We are also facing this issue .
Can you share some code that how you are doing this .
Are you using external code for killing and relaunching QTP and IE ?
Thanks in advance