Access violation reproduction

tullik

Access violation reproduction -- v.1.9.0.528 -- Vista BE (not SP1)

It may help with debugging to know the following:

1. Start an instance of PowerTools; drag the main window #1 to the side an inch or so.

2. Start another instance of PowerTools (main window #2).

3. Close the 2nd instance.

4. Result: the 2nd instance ends, and a few seconds later, the 1st instance fails with two "Access violation" pop-ups.

5. Do 1 and 2 again.

6. Close the 1st instance.

7. Result: the 1st instance ends; the 2nd instance is OK and can be used to run tools.

8. The sequences have the same result every time.

02-14-2009_20-28-12.jpg

leonardo

tullik wrote
Access violation reproduction -- v.1.9.0.528

It may help with debugging to know the following:

1. Start an instance of PowerTools; drag the main window #1 to the side an inch or so.

2. Start another instance of PowerTools (main window #2).

3. Close the 2nd instance.

4. Result: the 2nd instance ends, and a few seconds later, the 1st instance fails with two "Access violation" pop-ups.

5. Do 1 and 2 again.

6. Close the 1st instance.

7. Result: the 1st instance ends; the 2nd instance is OK and can be used to run tools.

8. The sequences have the same result every time.

02-14-2009_20-28-12.jpg

I can confirm the test Tullik did on my Win XP-P SP3 laptop:

Access violation at address 7C91B1FA in module 'ntdll.dll' Write of address 00000010

tullik

Of course this issue also affects the reliability of PowerTools command line and automated tasks.

With such tasks, you don't always (only sometimes) get the "Access violation" pop-ups. Instead, the other task usually just ends abruptly, without any notice.

jv16

This problem should now be fixed, thank you for reporting! The fix will be included to the next released version which is due out early next week (probably Tuesday).

leonardo

jv16 wrote
This problem should now be fixed, thank you for reporting! The fix will be included to the next released version which is due out early next week (probably Tuesday).

In version 1.9.0.531 this problem is NOT fixed, test done with Win-XP-Professional

tullik

In v.1.9.0.540:

The Access Violation pop-up does not happen.

This happens:

If the second instance is closed first, it ends normally, then a few seconds later, it causes the first instance to suddenly end with no warning.

If the first instance is closed first, it ends normally, and the second instance stays up ready for work.