Registry Cleaner slow - cache problems

aagaard

I just installed jv16 PT 2010 2.0.0.961 on my Win7 x64 and discovered, that Registry Cleaner runs very slow. Before I have tested several beta-versions on a Win7 x64 running in virtual environment (vmware) and have not noticed the same problem. A registry cleaner run in the virtual environment took typical 20-22 seconds, but in my real OS a run takes typical 230 seconds.

First tegistry cleaner starts up going fast , but then it reaches a point where it stops counting keys/values analysed and just reads from hdd in a very long period of time (maybe 90% af total time used for a registry cleaner run), finally it get going analysing keys/values again and finishes shortly after. I seems as if registry cleaner uses most of the time reading informations it should be able to get from FileCache.dat.

I have tried to flush the caches several times and I noticed, that FileCache.dat comes out with different size each time after a flush (i.a. 550 kb, 623 kb, 600 kb). Once after a flush it apparently build a cache more usefull than before and registry clean ran in only 42 seconds (before about 230 seconds).

I suspect the problem with the speed relates to filecache somehow and this problem should be fixed ASAP considering the negative experience new users can get from this problem. But maybe I am the only one with this problem ???

jv16

Could you try to run the Registry Cleaner in Windows safe mode? I'm asking you to do this in order to eliminate the possibility that any third party software is slowing down the scan. Many security related software can do this, such as Anti-Virus products.

aagaard

jv16 wrote
Could you try to run the Registry Cleaner in Windows safe mode? I'm asking you to do this in order to eliminate the possibility that any

third party software is slowing down the scan. Many security related software can do this, such as Anti-Virus products.

Results from registry run in Windows Safe mode:

Registry run: 220 seconds and still with the same problem

Rebuild cache (FileCache.dat this time 505 kb)

Another registry cleaner run with the new caches, 222 seconds

So it seems it has nothing to do with security products (I am using Microsoft Securiyty Essentials) or drivers.

Anything else I can try to help find the problem ?

jv16

Could you run the scanner with the Debug Mode enabled and send me the Debug Log?

aagaard

jv16 wrote
Could you run the scanner with the Debug Mode enabled and send me the Debug Log?

Have run scanner with debug-mode enabled.

I attach Debug Log and also a copy of FileCache.dat (so you can see if this file valid).

jv16

Thank you for the Debug Log.

According to it, everything seems to be running fine. The performance issue is most likely caused by some large piece of registry data that the Registry Cleaner Engine cannot handle in a smart way.

I'll do some changes and the issue is hopefully fixed with the next build.

jv16

The issue should now be fixed. I say "should" because I have not been able to reproduce the problem and therefore I cannot be sure whether the fix works either.

The fix will be included to the next released build.

aagaard

jv16 wrote
The issue should now be fixed. I say "should" because I have not been able to reproduce the problem and therefore I cannot be sure whether the fix works either.

The fix will be included to the next released build.

Thank you - I wait for the next release and let you know if it works.

aagaard

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.

aagaard

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.

leonardo

According to the developer the objective for build 964 is:

1. To bypass the 'Installation problems with certain AV products' in build 963 .

2. Safety improvement: Running the Clean and Fix my computer or File Cleaner with the safest scan option will no longer list any files relating to Windows,

nor any DLL or other executable files.

It is my understanding that hardly any other fixes are imbedded in build 964.

ADDED: see http://www.macecraft.com/news/197/

aagaard

Leonardo wrote
According to the developer the objective for build 964 is:

1. To bypass the 'Installation problems with certain AV products' in build 963 .

2. Safety improvement: Running the Clean and Fix my computer or File Cleaner with the safest scan option will no longer list any files relating to Windows,

nor any DLL or other executable files.

It is my understanding that no other fixes are imbedded in build 964.

Sorry, then I have to repeat it all at a later time.

By the way - I wonder, where do I see what the objective is with a new build and how can I be sure that this particular problem is not forgotten.

I can't trust bugtracker on this - only some of the reported issues shows - other issues seems to be ignored for some reason.

This issue has been reported via bugtracker long time ago, but I have never been able to find it under bugtracker again.

This makes me feel very unsecure - is the problem recognised/addressed or not. Maybe it is not considdered a problem at all because I am the only one who has reported this problem - I can't be sure. But to me it is a really annoying problem which indicates something does not work proberly.

I have reported another problem (Clean and Fix leads to application crash every time) and this also was reported via bugtracker and came out with the message, that the problem should now be fixed. According to you this seems not to be the case, so now this bug is out of bugtracker but not fixed.

It seems to me, that the handling of bugreports could use some improvements.

leonardo

Aagaard wrote
Leonardo wroteAccording to the developer the objective for build 964 is:

1. To bypass the 'Installation problems with certain AV products' in build 963 .

2. Safety improvement: Running the Clean and Fix my computer or File Cleaner with the safest scan option will no longer list any files relating to Windows,

nor any DLL or other executable files.

It is my understanding that no other fixes are imbedded in build 964.

Sorry, then I have to repeat it all at a later time.

By the way - I wonder, where do I see what the objective is with a new build and how can I be sure that this particular problem is not forgotten.

I can't trust bugtracker on this - only some of the reported issues shows - other issues seems to be ignored for some reason.

This issue has been reported via bugtracker long time ago, but I have never been able to find it under bugtracker again.

This makes me feel very unsecure - is the problem recognised/addressed or not. Maybe it is not considdered a problem at all because I am the only one who has reported this problem - I can't be sure. But to me it is a really annoying problem which indicates something does not work proberly.

I have reported another problem (Clean and Fix leads to application crash every time) and this also was reported via bugtracker and came out with the message, that the problem should now be fixed. According to you this seems not to be the case, so now this bug is out of bugtracker but not fixed.

It seems to me, that the handling of bugreports could use some improvements.

I really do not think that your sent Debug Log.html and DebugReport.txt to Bugtracker are lost or a waste of your time. I do not see why you should repeat it all at a later time. These reports represent your current jv16PT build 964 situation. A new release does not necessarily contain ALL fixed bugs up till the time of release!

For the jv16PT build 964 objectives see topic http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4154&start=30#p25056 and http://www.macecraft.com/news/197/

aagaard

For the jv16PT build 964 objectives see topic viewtopic.php?f=26&t=4154&start=30#p25056 and http://www.macecraft.com/news/197/

Thanks for the links - just discovered the news link on http://www.macecraft.com - a place where I normally never look. My fault - no excuses.

I still dont feel safe about the bug-reporting thing. The bug in this topic i.e. was reported about a month ago and still not fixed.

So is it forgotten, is it just considered 'not important' or something else. It really would be nice to know.

leonardo

Aagaard wrote
I really do not think that your sent Debug Log.html and DebugReport.txt to Bugtracker are lost or a waste of your time. I do not see why you should repeat it all at a later time. These reports represent your current jv16PT build 964 situation. A new release does not necessarily contain ALL fixed bugs up till the time of release!

For the jv16PT build 964 objectives see topic viewtopic.php?f=26&t=4154&start=30#p25056 and http://www.macecraft.com/news/197/

Thanks for the links - just discovered the news link on http://www.macecraft.com - a place where I normally never look. My fault - no excuses.

I still dont feel safe about the bug-reporting thing. The bug in this topic i.e. was reported about a month ago and still not fixed.

So is it forgotten, is it just considered 'not important' or something else. It really would be nice to know.

I think that Bug Tracker bug report= 426138 describes your 'cache performance problem'.

Details of bug 426138; Status: Fixed, Fixed version released.

Reported on 30.06.2010; Reported by te...@gmail.com

Bug summary: Registry Cleaner runs very slow

Also see topic: http://www.macecraft.com/phpBB3/viewtopic.php?f=26&t=4089#p24967

However the fix did not solve your problem, as you later reported for build 963 and 964.