I'm sure the devs are aware and the next version will clean this chrome. The problem is that Google keeps changing things faster than outside developers can keep up. The developer's get dev branch when everyone else does, that means that release of dev branch starts to be cleaned by the version of ccleaner that the devs are working on at the time. And thus you need to wait till the version to come out. Ccleaner is released monthly unless a FATAL bug is found; lack of cleaning of a single program is, by anybody reasonable's call, not a fatal bug.
What if Chrome developers change the history/cache data location? (internally in an Chrome installation) right, then Ccleaner wouldn't know the new location and so fails to clean, because ccleaner attempts to clean an location where no history is saved anymore (they changed location)
Please read the big words above.
This topic was started with the complaint of CHROME SETTINGS CORRUPTION.
That is a SIGNIFICANT CONSEQUENCE of the Chrome developers deciding to put settings on the path that had been used for Junk,
and it is unfortunate that they decided to put their users settings at risk.
You are now grumbling about a DIFFERENT AND TRIVIAL NO-HARM CONSEQUENCE of a failure to clean history.
You might be disappointed that history is not being cleaned now, but THAT is not what you started this topic with.
It is the fault of Chrome that it creates history which you prefer to eradicate,
and I am sure that Piriform will address this different consequence.
No user action will be needed to remove history, other than using a CCleaner version that catches up with Chrome's chaos.
Corruption of Chrome Settings is quite likely to impact the normal use of Chrome as a browser, and some users may have difficulty restoring normality.
Failure to remove history will not impact the normal use of Chrome as a browser.
That makes failure to clean a TRIVIAL TEMPORARY problem when compared to your original complaint of Settings Corruption.
Alan_B, 'complaint, complaint, complaint'
Everything ok with u mate?
As someone who found this thread because my Chrome profile was corrupted after using CCleaner last night, I'd like to thank BugReport for the submission so I could verify that it actually WAS CCleaner that actually caused all my headaches. I was unaware that a month old version of CCleaner would have such an impact on my (recently auto-updated) stable channel of Chrome. In fact, I think a good number of users would have benefited from being informed of this issue. Perhaps, changing the auto-update message to STRONGLY ENCOURAGE updating to avoid program corruption might help in the future? I wasn't even really sure why Chrome lost all my bookmarks, extensions, passwords, etc until I realized I had run my weekly CCleaner session. I resorted to a year old backup profile, but I'm really at a loss how the ball was dropped on this one.
Alan_B, I'd like to note that you really haven't added much to the conversation of this thread. You've been combative and downright condescending. Next time someone submits a bug, how about allowing the devs to address the issue instead trying to butt in?
For anyone else, has anyone had success fixing their profile? Much to my chagrin, I've never synced my settings so all I have is a backup of my corrupted profile. I've looked into suggestions of fixing Chrome's SQLite databases, but everything I can find only works with Linux. Any help would be greatly appreciated.
I was unaware that a month old version of CCleaner would have such an impact on my (recently auto-updated) stable channel of Chrome. In fact, I think a good number of users would have benefited from being informed of this issue. Perhaps, changing the auto-update message to STRONGLY ENCOURAGE updating to avoid program corruption might help in the future? I wasn't even really sure why Chrome lost all my bookmarks, extensions, passwords, etc until I realized I had run my weekly CCleaner session. I resorted to a year old backup profile, but I'm really at a loss how the ball was dropped on this one.
Alan_B, I'd like to note that you really haven't added much to the conversation of this thread. You've been combative and downright condescending. Next time someone submits a bug, how about allowing the devs to address the issue instead trying to butt in?
For anyone else, has anyone had success fixing their profile? Much to my chagrin, I've never synced my settings so all I have is a backup of my corrupted profile. I've looked into suggestions of fixing Chrome's SQLite databases, but everything I can find only works with Linux. Any help would be greatly appreciated.
This was not an issue for the stable channel of Chrome until it was auto-updated.
Your thinking on the Auto update message is a little too small.
It would be appropriate to change the message to indicate that EVERY improvement in the cleansing power of CCleaner includes the possibility that it might cause harm instead of good,
and this applies to ALL browsers and also all non-browser applications.
EVEN MORE IMPORTANT in this particular case, but also relevant to all non-Chrome browsers, and indeed to all non-browser applications,
if such browsers and applications are auto-updated they might suffer harm from the last installed version of CCleaner if they place important things where "junk" was previously held.
N.B.
My posts have not delayed the developers.
Alan_B, I'd like to note that you really haven't added much to the conversation of this thread. You've been combative and downright condescending. Next time someone submits a bug, how about allowing the devs to address the issue instead trying to butt in?
I agree on this, and Alan, yeah, please cut this off from here.
You aren't representing Piriform or CCleaner developers, but you jumped into an bug report thread with all your negativeness and 'complaint' talk.
It is not that you're gonna be praised if you show arrogance in a thread where CCleaner users unite that have one and the same problem. I hope that you can quit putting your off-topic and criticizing words in here and that we don't need to get an forum mod in here.
since posts are now degrading into personal attacks and the reason for the problem seems to be known, is it time to close this thread ?
since posts are now degrading into personal attacks and the reason for the problem seems to be known, is it time to close this thread ?
I agree
As we seem to have reached a point where no further benefit can be gained by keeping this thread open, I'll close it now.