Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 19706 by pawliger: User-applied update behavior is confusing,
frustrating, and may put users at risk
http://code.google.com/p/chromium/issues/detail?id=19706
Chrome Version : 4.1.201.1
Other browsers tested: Firefox 3.5, Safari 4, Camino 2
Safari 4: OK
Firefox 3.x: OK
IE 7: OK
IE 8: OK
What steps will reproduce the problem?
1. Wait for an update to be available for the currently running version of
Chrome
2. Wrench menu> About Chrome, click to update
3. After the "Close all Windows" dialog appears, Wrench menu> Exit
4. Immediately relaunch Chrome
5. Wrench menu> About Chrome
6. You have a very high chance (though not 100%) of seeing Update is
available or may see the
Close all windows to start using the new version of Chrome dialog again
7. On Windows, running Task Manager while Chrome appears to exit after step
3, shows there
are multiple chrome.exe processes still running for sometimes as long as a
minute after all
visible Chrome windows are closed during the "exit". It could be these
processes are re-used in
step 4 when Chrome is relaunched.
What is the expected result?
After applying the update, for Chrome to definitively be the updated
version when it is next run.
What happens instead?
Depending on timing, memory, machine load, and numerous other factors, you
have a random
chance of using the new version, or perhaps re-using the old version, or
perhaps some mash-up
of new and old.
Please provide any additional information below. Attach a screenshot if
possible.
This flies in the face of Chrome's "always being running the latest and
greatest and safest
version" mantra and should be addressed. Aspects of some of this behavior
seem to be open in
other bugs and this bug attempts to state the problem in terms of the
expected user behavior
without suggesting implementations to fix it.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
