jv16 PowerTools 2010 Beta6 released! (Latest build: 938)

doogie

I just ran the Unit Testing Tool. 6 errors found then it crashed.

BugReport and DebugLog attached.

thmck

I ran the Unit Testing Tool. 11 errors found then it crashed.

jepe

jv16 wrote

That is good news! Does the Unit Testing Tool also run without any errors?

For me the Unit Test stopped with an error message, as far i could see, after the third run of Test RegistryDataAnalyzer.

Some more observations:

- During the test I could notice that there were 1 error of Test RNG (at 153 s of the run) and 2 errors of Test TBackupManager (at 193 s).

But these errors I can't find in the Debuglo file, as between 0 and 297 seconds there are no registrations of such errors.

- The most of the errors are Test RDA FPO items, which can be found in the Debuglog file

- When the Test RegistryDataAnalyzer started for the first time, it activated my 3 1/2" drive again and again. I could stop it by inserting a disk.

Jean-Paul

leonardo

Leonardo wrote
jv16 wrote
Leonardo wrote

In XP-Pro-SP3 with beta6-v932 Registry Cleaner is working again as expected!

That is good news! Does the Unit Testing Tool also run without any errors?

I ran the Unit Testing Tool for over 2 hours!!

Observations from this test:

1.Windows Task Manager shows jv16PT.exe completely monopolizing one of my two processors (constantly >50% cpu usage)

2. Memory usage of jv16PT.exe is constantly growing up till 1.514.220KB. At that point jv16PT.exe "stops" running.

It does NOT crash, does NOT really die. I could 'close' the Unit Testing Tool in the normal way by hitting the 'close botton'.

The reason the Unit Testing Tool stops running is the lack of sufficient memory to continue.

My laptop has 'only' 2048MB of hardware memory and 1024MB defined virtual/paging memory.

Up till the "out of memory" occured the Unit Testing Tool detected 144 errors!

See the attached Unit_Test_v932.zip file for 5 screenshots taken during the process and 3 debug/log data files.

One debuglog was saved BEFORE closing the Unit Testing Tool.

The other debuglog was saved AFTER closing the Unit Testing Tool.

charlesn56

XP Home SP3

Registry Cleaner works great. Ran Registry Information, crashed upon exit.

leonardo

charlesn56 wrote
XP Home SP3

Registry Cleaner works great. Ran Registry Information, crashed upon exit.

Confirmed, upon exit an acccess violation occurs.

akajohndoe

Running Windows 7 with a local username that contains a space (e.g.: XXXX X). Two forms of errors encountered: One, where the key/value/folder is not found due to the space and data trailing the space being dropped; Two, where the key/value/folder is not found due to the space being dropped and the trailing data appended.

jawz101

under speed up my computer, performance tweaks you have the setting to turn off performance counters however the value is incorrect. the dword value DisablePerformanceCounters should have spaces

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\

if I add the correct value of 'Disable Performance Counters' while perfmon is running it immediately stops counters

tullik

Version 2.0.0.932 on an x86 Windows 7 notebook

6. Initial Setup creates an empty SysCache.dat file

7. Registry Cleaner does not run (probably related to issue number 6).

On the above system, those issues are gone with this version.

tullik

Version 2.0.0.932 on an x86 Windows 7 notebook

230. C&FMC: invalid pointer operation when run twice in the same session. __ 932 x86 w7 (.)

*C&FMC IPO.zip

212. C&FMC: crashes when user chooses to abort during final analysis or while removing files. 922 x64 w7 |..| 932 x86 w7

Debug files show the "abort during final analysis" case.

*C&FMC IPO (1).zip

These similar items were in prior change logs:

6. Running "Clean & fix my computer" for the second time during the same session stops in an Access Violation. 779 x64 w7 (.) FDNW5

16. "Clean & fix my computer" causes AV/Invalid pointer operation when final analysis scan is aborted. 779 x64 w7 (.)

tullik

Version 2.0.0.932 on an x86 Windows 7 notebook

119. Registry Cleaner: Tools-->Compare results... aborts itself every time (message=: Operation aborted.). __ 678 x64 w7 |.| 932 x86 w7

This feature works now.

jv16

DooGie wrote

jv16 PowerTools AssertEx Log

12.05.2010 15

- AssertEx1 (RS) FAILED! Desc="TDebugLog.AddLogEntry, Entry="Start: Procedure TFileViewForm.OnGetInfo(Sender: TObject; FileInfo : TFileInfo; PossibleIndex : Integer);""

This bug is now fixed, thank you for reporting! The issue most likely have caused problems in the past, such as the column data of the File Tool not being filled.

jv16

charlesn56 wrote
XP Home SP3

Registry Cleaner works great. Ran Registry Information, crashed upon exit.

Issue confirmed and fixed. The same problem also occurs if user attempts to Abort the tool while it's working.

Thank you for reporting!

jv16

AKAJohnDoe wrote
Running Windows 7 with a local username that contains a space (e.g.: XXXX X). Two forms of errors encountered: One, where the key/value/folder is not found due to the space and data trailing the space being dropped; Two, where the key/value/folder is not found due to the space being dropped and the trailing data appended.

Could you give an example or two of such issue?

jv16

jawz101 wrote
under speed up my computer, performance tweaks you have the setting to turn off performance counters however the value is incorrect. the dword value DisablePerformanceCounters should have spaces

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\

if I add the correct value of 'Disable Performance Counters' while perfmon is running it immediately stops counters

You are indeed correct! This issue has now been fixed, thank you for reporting!

jv16

DooGie wrote
I just ran the Unit Testing Tool. 6 errors found then it crashed.

BugReport and DebugLog attached.

Thank you very much! I think the EOutOfMemory issue has now been fixed. If not, at least the next build contains more debug information that should make it easy for me to fix the issue.

jv16

jepe wrote
jv16 wrote

- When the Test RegistryDataAnalyzer started for the first time, it activated my 3 1/2" drive again and again. I could stop it by inserting a disk.

What is the drive letter for that drive? A?

jepe

jv16 wrote
jepe wrote
jv16 wrote

- When the Test RegistryDataAnalyzer started for the first time, it activated my 3 1/2" drive again and again. I could stop it by inserting a disk.

What is the drive letter for that drive? A?

Sorry I forgot to indicate ... yes it's "A".

Jean-Paul

jv16

jepe wrote
jv16 wrote

What is the drive letter for that drive? A?

Sorry I forgot to indicate ... yes it's "A".

Jean-Paul

I can't be sure because I cannot reproduce the issue, but the problem should now be fixed. I'll do a few more fixes and then it's time for a new beta build.

siliconman01

Windows 7 x64 Professional, PT build 932

The unit test errors are attached. Eight(8) errors were found. I finally stopped this test after 3100+ seconds because the test appeared not to be progressing. jv16 had commandeered over 500 mbytes of RAM memory. Also note that when I "closed" the Unit Test and exited jv16, it did not exit from memory. I had to kill it with the Task Manager.

Does the Unit Test honor the global ignore list for disks not to be accessed?

« Previous Page Next Page »