Comment #13 on issue 1565 by [EMAIL PROTECTED]: Don't make GoogleUpdate always-resident http://code.google.com/p/chromium/issues/detail?id=1565
One of the reasons that doesn't work is that we'd like the update mechanism to be able to recover from a bad update being pushed out. If we push out an update that immediately crashes on 2% of user machines, then linking the update mechanism with software launch will wind up stranding those users. We agree with the sentiment behind this report (we'd prefer not to keep anything resident, even if it's as small as GoogleUpdate), and as kucchal said, the team is looking into alternatives. -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
