for the first time ever, your latest 323 build hangs up on the chrome section of your cleaning mode, then causes chrome to crash
after unintall and reinstall several times, same problem, so i reinstalled the prior build (i had kept a copy of that exe file for 322.
1) has anyone else experienced this?
2) will restore registry continue to work after all these install/uninstalls? (the points seem to be there.)
windows 7 home premium on hp notebook 2g ram
same here - downloaded 3.23 (my first experience of the product) and my beautiful, tuned laptop now runs like a dawg with 3 paws in chrome.
now im back on ie9, which still seems the same as before.
lenovo t410 / 4gb ram / win 7 ultimate with all ms patches + mse resident.
love a cure for this one please, before i rebuild + retune
at first i thought the latest update had trashed the computer of the big boss - mrg
and listened for heads rolling
yeah, Alan,I thought that too.
these two post sound like separate issue.
To the first poster it sounds like not all instances of chrome are fully exited. This usually occurs if you are running chrome sync or chrome print. Do you have either of these features running in chrome?
Yep, I reverted to 3.22.1800 due to issues with Chrome.................Sometimes it's best not to keep "improving, just to say we improved".
D bone your issue may or may not be the same, however your "advice" here does not help the original poster, nor any member in attempting to debug the issue.
It wasn't advice, but rather an observation that newer isn't always better. There was nothing wrong with the performance of the prior build, and in the quest to find a few more kb's of junk in Chrome, there now seems to be a step backwards. That might help the designers thought process for the next build.
before taking a drastic and unhelpful step let's wait till we get an answer to my preliminary question
To the first poster it sounds like not all instances of chrome are fully exited. This (crash you're having) usually occurs (because of this) if you are running chrome sync or chrome print. Do you have either of these features running in chrome?
D bone, you have your own thread, which a reply has been made. Please run the latest ccleaner analysis, exclude the file mention there and try to clean. Your issue is different and you are possibly causing confusion if the original poster returns
I want to be clear, that not only did I have the issue that I made my thread about, but I also experienced the same issue as the OP of this thread too, I just didn't make a thread about it because I reverted to the prior build, which fixed all of my issues. I don't want to come off as confrontational, and hope I'm not seen that way, but I just wanted to make sure you knew that I too experienced the problem in this thread.
I will monitor this thread, as well as the one I started in hopes of a fix. Thanks for your time.
This usually occurs if you are running chrome sync or chrome print.
May help to untick in the 'Advanced settings' of Chromium-based browsers the option: Background apps
What Background apps does if enabled:
Continue running background apps when "insert Chromium-based browser name here" is closed