|
Recovery from WinRunner Crashes
WinRunner operates in these Windows processes:
Image Name Mem
Usage v7.6 File
Bytes v8.2 File
Bytes
wrun.exe (with no scripts loaded) 18,420 K 4,157,490 4,628,530
crvw.exe (WinRunner Record/Run Engine) 7,956 K 802,865 815,153
MDM.EXE (Microsoft Windows Machine Debug Manager) startup program (not a Task Manager process) 3,600 K - -
NTVDM.EXE (six_agnt.exe and wowexec.exe) 3,416 K - -
If WinRunner crashes and you don't want to reboot, press Ctrl-Alt-Del, select the Task Manager, click Processes Tab, Image Name. Then click on each of these processes (if they exist) and click "End Process" on each of the above. This should solve this error message in file wrstderr:
Error: open connection to CRV (-1). Exiting...
Exit WinRunner Often
WinRunner automatically creates a ".BAK" copy of script files it opens for editing. Save operations do not update this ".BAK" file. If WinRunner crashes, it will replace the current version of script files with their ".BAK" version.
So exit WinRunner after you make a lot of changes to avoid getting them wiped out.
Zip up your script directory before you open your script after a crash. It's a good idea to archive versions. Rename each file with a sequential number. Move them to an "arc" folder if you don't want to see them.
简单说就是关掉wrun.exe/ crvw.exe/NTVDM.EXE (six_agnt.exe and wowexec.exe) |
|