Is there a way you can make the IE Autocomplete Form History removal faster?
When its checked it takes 8.2 seconds to clean:
When its not checked it takes 2 seconds to clean(4 times faster):
All other settings are same and i made sure only certain files are in recycle bin(so results are fairly comparable)
Also the more there is to clean the more time this setting adds to the overall time.Especially after PC has been restarted(i restarted before each test)
Its not a Bug per se and i have unchecked it for now but still wanted to ask.
Maybe its some my system specific setting
Maybe it has something to do with the fact that im running Windows 7 N(Version where IE has been removed but core files are still present)
If Piriform could cut that time down to 5 secs, how would you spend the 3.2 secs you saved?
Understanding the constantly advancing efficiencies in software development, the time probably will be cut somewhat in future revisions.
After all, this is a free program, and I presume the developers are faced with time constraints on nonrevenue-producing programs.
I totally understand this.This isnt about the time it takes to clean.Obviously anything under 30 seconds is ok but i merely wondered what migt be causing this delay
huum 8.2 seconds, or 2 seconds, hummm lets see. I think i rather have the 8.2 seconds, this way I can get a beer and it won't foam up when I pop it open if I got it in 2 seconds.
Just kidding buddy, I just in a good funny mood today wishing Piriform would come up with even MORE great programs. TY Piriform.
I can't understand why that happens as I've never seen an issue with that particular setting. I would think you would need to do an awful lot of form-filling each time you browse for the problem to be consistent.
I appreciate why you've posted it as the increase in time would niggle at me until I found out why.
Do you do a lot of form-filling every day?
EDIT: I'm not even sure if that's the right question to ask as I'm a bit puzzled with this one.
The major slow down I've noticed in the newest version is when using the winapp2.ini unofficial add-on. Disabling it by renaming it to something like winapp2.old allows CCleaner to speed through cleaning. With it enabled CCleaner takes at least 60 seconds, or even longer.
The latest versions of CCleaner have had different effects on different people. I was suffering quite a slowdown with Registry Mechanic until I removed it from winapp2.ini, and I clean it with an include now.
So gap is under 3 seconds.I used the same config file and restarted between tests.Since there is no hardware acceleration in virtual machine then there is obvious overhead but less than 3 seconds can be condsidered margin of error.So i think the problem does not exist there.
Must be Windows 7N specific then.Unfortunately i have no images of 7N to test in VM.
If it's just the latest CCleaner that does this, try a previous version. It's what some members, including myself, do until a newer release fixes a particular issue.
hi. been using ccleaner for a while now. never noticed before but see now that when the 'Autocomplete Form History' box is ticked, rundll32.exe shows (and continues to show) in task manager for each time ccleaner is run. if the box is not ticked, the same rundll32.exe shows briefly, but then disappears. makes no difference whether using full or slim version. why does this happen? sorry if dumb question or already answered.
hi. been using ccleaner for a while now. never noticed before but see now that when the 'Autocomplete Form History' box is ticked, rundll32.exe shows (and continues to show) in task manager for each time ccleaner is run. if the box is not ticked, the same rundll32.exe shows briefly, but then disappears. makes no difference whether using full or slim version. why does this happen? sorry if dumb question or already answered.
What OS and IE version? I've just checked on my machine (XP + IE8) and with Autocomplete checked rundll shows briefly then disappears.
(Without it checked it doesn't appear at all but you may just have an option checked that I don't)
hi. using XP Pro, all updated and IE 7.0.5730.13, all up to date as well. dont know why it does it or how long it has been doing it. bit weird i thought, certainly as it behaves as yours does, as long as that box is not ticked.
