The unit test errors are attached. Eighty one(81) errors were found. I finally stopped this test after 3600+ seconds although the test was slowly progressing (only about 50% completed). jv16 had commandeered over 1.6 gbytes 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.
jv16 PowerTools 2010 Beta6 released! (Latest build: 938)
Build 933 released:
http://www.macecraft.com/downloads/betas/jv16PT2010_Beta6_b933.exe
FYI: If you have been using Build 932, you should have got a notice about the new version when starting PowerTools, that is, without the need to use Help > Check for updates.
Here is the Change Log of Build 933:
Issues Fixed (since the original Beta6 release)Known issue fixed: Anti-Malware feature is not yet ready for testing.
Note: If you want to test the Anti-Malware feature and make sure it can detect something, you can use the test file from http://www.eicar.org/anti_virus_test_file.htm
Issues Reported (numbers continue from previous version)
119. Registry Cleaner: Tools-->Compare results... aborts itself every time (message=: Operation aborted.). __ 678 x64 w7 |.| 932 x86 w7
Issues Reported (new numbers)
1. Unit Test feature reports errors relating to "TestRNG"
2. Unit Test feature reports errors relating to "TestTBackupManager"
3. File Recovery can show an errir message: "The following information must be provided in order to start: At least one search argument, you can use Files to find, Search by size and/or Search by date tabs." - there is no Search by date tab.
4. System Cleaner tool's window doesn't have a tool caption, nor does the tool exist in English.lng at all
5. The size and position of some or all tool windows are not correctly remembered.
6. Initial Setup creates an empty SysCache.dat file
7. Registry Cleaner does not run (probably related to issue number 6).
8. Any of the file tools can report the following error message: "AssertEx1 (RS) FAILED! Desc="TDebugLog.AddLogEntry, Entry="Start: Procedure TFileViewForm.OnGetInfo..".
9. Registry Info tool crashes to "Access violation at address 00863DD8" if Aborted, or if the tool has been fully run and then the tool window is closed.
10. "Disable performance counters" tweak does not work with the System Optimizer.
11. Unit Testing Tool can crash to EOutOfMemory while performing the "SafetyNet.IsDangerousRegKey" test.
12. Unit Testing Tool can report errors relating to "Error: TestRDA FPO item ..." and "Error: TestRDA: FPO rate of X is larger than accepted!".
13. When Unit Testing Tool's RegistryDataAnalyzer Test started for the first time, it activated my 3 1/2" drive again and again. I could stop it by inserting a disk.
Issues Not Reported AFAIK
1. If a new version of the program is available, and you start Help > Check for updates right after starting the program, you might see a message "You are currently using version "{1}". A newer version "{2}" is available. Would you like to get more information about the new version?". If you click Yes, the already opened Check for Updates windows will close, start again and check again for a new version. The second time the popup does not occur.
2. The Check for Updates window lacks its icon.
3. File Tool's File Analyzer feature doesn't look right, all the text captions are wrong and do not originate from the English.lng
4. Mass File Renamer's Convert Case feature cannot be accessesd because the box is too small.
5. File Encrypter tool contains an incorrectly named button (Abort button says "AbortBtn").
6. File Organizer tool contains an incorrectly named button (Add button says "AddBtn").
7. Automation Tool: If you click Delete but then select No, the automation task is not deleted, but clicking Delete again doesn't do anything, the task is not deleted nor is the confirmation ever shown again.
8. If you abort the History Cleaner, it can crash to Access Violation.
9. Running Unit Testing Tool can cause the GUI to freeze for long periods of time.
10. "RegistryDataAnalyzer" test in Unit Testing Tool seems to do nothing, and causes the tool to freeze for long periods of time.
11. File Tool's Columns > Checksums features do not work, no CRC32, SHA1 or MD5 of the files is ever displayed on screen.
12. If there are problems with connectivity, the Anti-Malware feature can be incorrectly installed and trying to use it causes the program to crash.
13. After Anti-Malware feature has been once installed, it can no longer be updated (i.e. it doesn't ever receive any information about updated signature files).
Improvements Done
1. Improved the Check for Updates window content handling.
2. It's now possible to send messages over the Internet to the Main Window of PowerTools, without the need of user clicking to Help > Check for Updates.
3. Increased the size of the Unit Testing Tool's window.
4. Clicking Abort now closes most of the tool windows - there is no need to show an empty list of results to the user if the user has clicked Abort.
5. Improved the detection of incorrect / corrupted translation file.
6. The program now saves a separate Debug Log of the first run, in order to catch any possible bugs that occur during the Initial Setup.
7. Added debug code in order to better track any "AssertEx Failed!" error messages.
8. Added more debug to better detect problems with FileCache and SysCache creation and loading.
9. Added a SelfTest feature to the Unit Testing Tool, it will detect any missing or corrupted files from PowerTools' installation directory.
10. Improved the amount of information the Anti-Malware tool's Update feature gives during the update process.
Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.
There must be some major memory leak problems in the Unit Test component. Systems with low RAM quantities definitely will have major problems running the Unit Test. As I stated in my previous post on B932, the RAM useage was up to 1.6 gbytes on my Win 7 x86 system....and growing.
And I do not think the Unit Test component is honoring the Global Ignore List disks because I am seeing errors in the log that reference disks that are in the GIL on both Win 7 x86 and Win 7 x64.
when running the registry cleaner, after analysis has completed & it shows the scan results dialog- if I check the box to not show the dialog in future scans it always still shows up
windows 7 x64
jawz101 wrotebuild 933
when running the registry cleaner, after analysis has completed & it shows the scan results dialog- if I check the box to not show the dialog in future scans it always still shows up
windows 7 x64
Confirmed with XP-Pro SP3 and build 933. This was also true for build 932
C&FMC Access Violation during 'fix' of errors/files found in the scan.
Unit Test error debug log and crash bugreport.
Running Registry Information for the second time (in the same jv16PT session) does not finish. But Registry Information can be 'closed' normaly.
see attached .zip file with debug data + screenshot of last displayed image of Registry Information.
Unit Test error debug log and crash bugreport.
siliconman01 wroteAnd I do not think the Unit Test component is honoring the Global Ignore List disks because I am seeing errors in the log that reference disks that are in the GIL on both Win 7 x86 and Win 7 x64.
This is correct, and the issue is now fixed. Thank you for reporting!
jawz101 wrotebuild 933
when running the registry cleaner, after analysis has completed & it shows the scan results dialog- if I check the box to not show the dialog in future scans it always still shows up
windows 7 x64
Good catch! This is now fixed, thank you for reporting!
siliconman01 wroteWindows 7 x86 Professional, PT 933
Unit Test error debug log and crash bugreport.
The Out of Memory error should now be fixed. Thank you for reporting!
jv16 wrotesiliconman01 wroteWindows 7 x86 Professional, PT 933
Unit Test error debug log and crash bugreport.
The Out of Memory error should now be fixed. Thank you for reporting!
I do not know if this is still of value to you, but I ran the Unit Testing Tool with XP-Pro-SP3 and b933.
The tool finished for ~75% before the 'out of memory' occured.
At that time jv16PT.exe had found 4 errors and was using 1.75GB memory, as reported by the Winows Task Manager!
Attached are the Debuglog + Screenshot just before the moment of the 'out of memory' situation.
Around 16 errors thrown up then the app crashed. An out of memory error is shown in the log, this on a PC with 6GB of RAM.
Reports attached.
C&FMC Access Violation during the 'abort' of second run
1) No directories found
In E:\Program Files I have a subdirectory "Ini Translator".
When I do a search with Directory Finder for that directory, the tool doesn't find it.
Tab "Directories to find" => "Ini Translator" entered
Tab "Search in" => E:\
Tab "Options" => nothing checked
Tabs "Search by size", "Search by contents", "Search by date" => nothing checked
What am I doing wrong?
When I enter *Ini Translator* or *Ini Translator the tool finds the directory, but in previous versions of jv16 PowerTools it was not necessary to put those "*"'s before and/or behind the words.
Besides it's not possible to let the tool search for several directories simultaneously: e.g. when I enter "*Ini Translator;*Euroglot" the tool only finds the latter.
2) Blue links in warnings do not work
When I don't put anything in the tab "Search in" I get the warning message: "At least one source directory". That's normal. But when I double click that warning (blue underlined link) nothing happens while normally it should jump to the tab "Search in".
-- Registry Cleaner in Reference Mode
Win-XP generates an error message and wants to sent out a bugreport.
See attached .zip file for all gathered data.
Version 2.0.0.933 on an x86 Windows 7 notebook
231. Unit Test: errors detected. TestRDA (8 total, 2 in 4 modules), then out of memory.
8513 seconds; 1,958,951 tests.
*Unit Test out of memory.zip
Testing Report of jv16 PowerTools 2010
* Hash: A2692A405DD6D9405AA4F0E15986A7D0
0 s. - The tests will use C:\ for storing temporary data, testing access to the drive...
0 s. - ...The program has full access to C:\ drive!
0 s. - Testing Started...
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - Error: Critical system backup 1 corrupted! : 4 Par1 = 17197 Par2 = 465
0 s. - Error: Critical system backup 2 corrupted! : 6 Par1 = 124048 Par2 = 1752
0 s. - SelfTest Done
0 s. - TFileList Test Done
131 s. - StringListFunctions Test Done
132 s. - IsDangerousKey Test Done
452 s. - FileTools Test Done
480 s. - RNG Test Done
510 s. - ExtractFilenameEx Test Done
554 s. - TBackupManager Test Done
558 s. - TSettingsManager Test Done
842 s. - RDA Eff rate: 91.77%, FPO rate: 0.00%, FNE rate: 16.45%
855 s. - Error: TestRDA FPO item: "@d:\Users\protect.englishpJCAA" -123 / 123 %123% 432" : 1 Par1 = 0 Par2 = 0
917 s. - Error: TestRDA FPO item: "%d:\Users\protect.englishn*{/´@ %123" : 1 Par1 = 0 Par2 = 0
917 s. - Error: TestRDA FPO item: "-d:\Users\protect.englishä7ZyG" : 1 Par1 = 0 Par2 = 0
918 s. - Error: TestRDA FPO item: "'d:\Users\protect.englishvoDVj" : 1 Par1 = 0 Par2 = 0
918 s. - Error: TestRDA FPO item: "d:\Users\protect.englishi8Lå|Ug\" : 1 Par1 = 0 Par2 = 0
1198 s. - Error: TestRDA: FPO rate of 0.01 is larger than accepted! : 5 Par1 = 0 Par2 = 0
1198 s. - RDA Eff rate: 85.46%, FPO rate: 0.01%, FNE rate: 29.06%
1198 s. - RegistryDataAnalyzer Test Done
1204 s. - StringTools Test Done
Basic System Setup
Windows version = 6.1.7600
Windows 7 = True
Windows Vista = False
Windows XP = False
Windows 2000 = False
Windows 9x = False
Windows 64 bit = True
Computer name = Piaqt