Eliminate all code related to the AutomaticProfileResetter.

chrome/browser/prefs/browser_prefs.cc

Index: chrome/browser/prefs/browser_prefs.cc
diff --git a/chrome/browser/prefs/browser_prefs.cc b/chrome/browser/prefs/browser_prefs.cc
index 28fa4634905442ff09fd116333178016a2eaf589..f37fdeff802a4e1352b149d5a3f0811d651305d2 100644
--- a/chrome/browser/prefs/browser_prefs.cc
+++ b/chrome/browser/prefs/browser_prefs.cc
@@ -126,7 +126,6 @@
 #include "chrome/browser/android/new_tab_page_prefs.h"
 #else
 #include "chrome/browser/notifications/sync_notifier/chrome_notifier_service.h"
-#include "chrome/browser/profile_resetter/automatic_profile_resetter_factory.h"
 #include "chrome/browser/ui/autofill/generated_credit_card_bubble_controller.h"
 #endif
 
@@ -271,7 +270,6 @@ void RegisterLocalState(PrefRegistrySimple* registry) {
 #endif  // defined(ENABLE_TASK_MANAGER)
 
 #if !defined(OS_ANDROID)
-  AutomaticProfileResetterFactory::RegisterPrefs(registry);

[battre, 2014/05/08 11:46:14]

The preference should be cleared in MigrateUserPrefs().

[engedy, 2014/07/30 09:07:21]

I have removed the respective prefs completely.

Could you please confirm that it is okay to have some values lying around in the
Preferences file that are no longer registered?

[battre, 2014/07/30 09:11:08]

As I said above, I think the policy is to clear it in MigrateUserPrefs() for one
milestone so that we don't add cruft to the prefs file.

[engedy, 2014/07/30 11:45:11]

Done. I have added code to clear both the local state and user preference, and
also the file that might have been stored to the profile directory.

As discussed offline, I have verified manually/locally that it works. I also
tried it out that just unregistering the preference is not sufficient: the value
will be unreachable from Chrome, but it gets written back when the JSON file is
saved to disk.

   BackgroundModeManager::RegisterPrefs(registry);
   RegisterBrowserPrefs(registry);
 #if !defined(OS_CHROMEOS)