History Cleaner, too many remove attempts

tullik

History Cleaner, redundant error messages after removing Java cache files

Edit: topic renamed 13 September 2008 -- link to change in emphasis: http://www.macecraft.com/phpBB3/viewtopic.php?f=15&p=16328#p16325

Issue #1 - the tool counts the files in the Java cache twice.

Issue #2 - the tool removes and backs up all the files, but then attempts to do it again. As a result, the program slowly produces thousands of error messages -- a lengthy process.

07-31-2008_10-45-30.jpg

07-31-2008_10-45-50.jpg

History Cleaner Java cache messages.zip

jv16

The problem of the History Cleaner listing some items more than one time is now fixed. I didn't create any special checks for Java cache but created a general solution that makes it impossible for duplicate items to be listed in the results.

Thank you for reporting! The fix will be included to the next released version.

tullik

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.

berny

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.

jv16

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.

tullik

v.1.8.0.468

History Cleaner works again, but the issue where the tool counts files more than once, then tries to delete the items again after it has already done so, is not fixed.

That is, the "general solution" did not work. Or perhaps it was deferred to get History Cleaner operability back with less risk?

A workaround when you get the very slow sequence of error messages is to click "Abort" when the progress indicator is half way done, then run the tool again to make sure what it did ...

redseujac

Confirmed

here.

jv16

I haven't been able to reproduce the problem myself so I can't be sure, I but did found and fixed more than one bug from the History Cleaner that could cause problems like this.

So, thank you for reporting and please let me know after you have tested the next version! The next version will be released later in this month.

tullik

History Cleaner, too many remove attempts v.1.8.0.472

History Cleaner now clears the 100s (or 1000s) of files in the java cache nicely.

There is one small residual issue. Namely:

*** Apparently there may be a background process which has a lock on a file.

*** In this case, one message like the five shown below is appropriate.

*** However, the four extra attempts to remove the file are not necessary.

: Failed to remove "C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-"! Windows core returned the following error: "The process cannot access the file because it is being used by another process."


: Failed to remove "C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-"! Windows core returned the following error: "The process cannot access the file because it is being used by another process."
: Failed to remove "C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-"! Windows core returned the following error: "The process cannot access the file because it is being used by another process."
: Failed to remove "C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-"! Windows core returned the following error: "The process cannot access the file because it is being used by another process."
: Failed to remove "C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-"! Windows core returned the following error: "The process cannot access the file because it is being used by another process."

: All done! 0 B of data was removed (0 files, 0 directories, 0 registry entries and 0 registry keys).

09-13-2008_03-35-57.jpg

09-13-2008_03-45-26.jpg

tullik

v.1.8.0.472

Here are the debug logs for this issue.

Files (HC 472).zip

jv16

tullik wrote
History Cleaner, too many remove attempts v.1.8.0.472

History Cleaner now clears the 100s (or 1000s) of files in the java cache nicely.

There is one small residual issue. Namely:

*** Apparently there may be a background process which has a lock on a file.

*** In this case, one message like the five shown below is appropriate.

*** However, the four extra attempts to remove the file are not necessary.

You are correct, even as the program attempts to delete the file multiple times there is no need to show the error message of failed delete attempt more than once per file.

berny

Hi Friends

The MRU cleaning tool in jv PT 2008 ver 1.0.8.472 seems to work perfectly here :)

1 - The problem of the History/MRU cleaner listing some items more than one time is now fixed.

2 - False error message mentioned below disapeared

"Failed to access "C:\Documents and Settings\myname\Application Data\Microsoft\Office\Recent\Maandmenu juni.lnk"!"

3 - The "looping" has also gone ....

You did a good job ... thank you :

Berny +++

tullik

jv16 wrote
... You are correct, even as the program attempts to delete the file multiple times there is no need to show the error message of failed delete attempt more than once per file.

The program also backs up the file once per message, also not necessary.

From message box:

: All done! 2.9 MB of data was removed (227 files, 0 directories, 0 registry entries and 0 registry keys).

Index.dat content:

ProgVersion=1.8.0.472

SyntaxVersion=1.4

DateTime=9/13/2008 3 PM

DateTimeEx=39704.6490333565

Text=Sun Java - 228 items

TypeCode=106

ID=43A789553A2135CFF8E6EEC57D6BC90505CF567D

From backup Files.dat:

Files=232

…

OrigFile=C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-

BackupFile=58a741e0-4b7e8506-3.8.28.3-

…

OrigFile=C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-

BackupFile=58a741e0-4b7e8506-3.8.28.3-_002246

OrigFile=C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-

BackupFile=58a741e0-4b7e8506-3.8.28.3-_001A99

OrigFile=C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-

BackupFile=58a741e0-4b7e8506-3.8.28.3-_0023DD

OrigFile=C:\Users\Owner\AppData\LocalLow\sun\java\deployment\cache\6.0\32\58a741e0-4b7e8506-3.8.28.3-

BackupFile=58a741e0-4b7e8506-3.8.28.3-_00046D

jv16

The problem is now fixed, thank you for reporting! The next released version will contain the fix in question.

tullik

jv16 wrote
The problem is now fixed, thank you for reporting! The next released version will contain the fix in question.

It is indeed fixed. The problems are gone in the just released RegSupreme Pro v.1.8.0.472.

The new RSP now has History Cleaner as an additional tool.