Is anyone aware of any memory leak problems with WinRunner 7 (I am using WR 7.01)? I know about the problem with crvw.exe 6.02 - but presumably that is fixed now?
I have a loop within a test that fails after about 100 iterations with "Not enough storage..." message, after which WR fails with an application error. WR is fairly unfamiliar terrority for me (I usually work with LoadRunner) - so if anyone has any general advice on WR functions not to call inside loops that would be appreciated.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by jseymour: I have a loop within a test that fails after about 100 iterations with "Not enough storage..." message, after which WR fails with an application error.<HR></BLOCKQUOTE>Use Task Manager or perfmon.exe to verify if it's really a WinRunner consuming memory. It could be an application also. Browsers are not 100% bulletproof either.
Update - further tests indicated that it could be the application that was not releasing resources, rather than WinRunner. To prove the point, we constructed a Visual Basic Script file (.vbs) that executed the same business process repeatedly. At around 100 iterations, lo and behold it failed too! Hence the focus of our attention is now on the application under test.