Open kathy-smith opened 12 years ago
What does "ran scenarios for 12 iterations" mean? The OPBM GUI is hidden during benchmark operations when the HUD is visible. There's no way to know if it was closed or open by viewing the screen. If the javaw.exe *32 process was still running (which it was because the HUD window was still visible), the OPBM GUI was still active as well, just set visible=false;
I added a fold called Ussue 106 scenarios to the z drive debug folder. It has a snap shot of the HUD and the debig file. I had to shut down the HUD through Task Manager.
The HUD doesn't just hang. It will hang if an external process is hung because it's waiting for that process to terminate. If it is hung, and cannot be terminated, then the HUD will appear to be hung as well because it's waiting for that process to finish.
This exact condition is why the watchdog is being written, to activate and forcibly shut down an external process after a long period of inactivity, something far beyond what's expected on even a slow system.
Am I understanding this correctly? A failure occurred the result of #74, which then caused Windows being unable to reboot?
Yes.
This is a side-effect of #74, and not its own issue.
The Firefox un-installer appears to be the cause of this failure also.
Van, please take a look at the firefox uninstaller on these SUTs that are seeing failures. The uninstaller seems to be the cause of the hang, indicating the uninstaller process never terminates.
I will test the Firefox installer/uninstaller this afternoon.
I tested the Firefox installer/uninstaller by running the atoms repeatedly in a batch file with no errors encountered.
Ran scenarios for 12 iterations. Windows tried to shut down at the end, but couldn't as the OPBM(HUD) would not close. OPBM GUI was closed.