search

van-smith / OPBM

Open Productivity Benchmark
1 stars 0 forks source link

HUD triggered an access violation prior to reboot #65

Closed van-smith closed 13 years ago

van-smith commented 13 years ago

The HUD triggered an access violation message which appeared immediately before reboot on the Llano SUT when running an Official Run from the command line.

The system rebooted and is running tests.

ghost commented 13 years ago

How do you know it was the HUD that triggered an access violation?

van-smith commented 13 years ago

Because that is what the access violation message box stated.

van-smith commented 13 years ago

This bug was encountered again on the Llano SUT. This time I was running an Official Run (sans Chrome install/uninstall) from the dev GUI and the message box appeared after the apparent successful completion of run 1.

Again, the system rebooted soon after this and is now running run 2.

van-smith commented 13 years ago

This occurred again on the Llano SUT when running an Official Run from the dev GUI.

ghost commented 13 years ago

Have been unable to reproduce this error. Posted a potential fix.

Added test for rebooting condition to not call a persist-on-top opbm32/64.dll function for the HUD when in that state. Added try catch around some opbm32/64.dll functions which may be causing that issue as processes are going out of scope.

van-smith commented 13 years ago

I have not encountered this failure in weeks.