Comment #14 on issue 1565 by omattos: Don't make GoogleUpdate always-resident http://code.google.com/p/chromium/issues/detail?id=1565
erikkay: You could run the update app on program startup AND on a windows schedule (say once per week). That way if an update goes bad, it can be repaired automatically at the next scheduled updater run. Alternatively, one could keep the updater resident from the time of the update until the next successful run of the program to ensure it's correctly working, and if it isn't correctly working (ie. doesn't start) then it could re-update to get a working version. I believe it's also important that if no google apps have been used in a while (say 6 months) that the google updater service should never run. If the user just installed chrome to try it out, and leaves it installed but no longer uses it, the program shouldn't use any system resources, even temporarily. -- 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 -~----------~----~----~----~------~----~------~--~---
