Add fallback behavior if the last used profile cannot initialize

chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index b463e4e56139110680514521778b24c4c26363aa..8e0fb0e502bf82b74dd1f3bddcd820100d3006de 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -5230,7 +5230,7 @@ Keep your key file in a safe place. You will need it to create new versions of y
       <message name="IDS_FLAGS_SAVE_PAGE_AS_MHTML_DESCRIPTION" desc="Description of the 'Save Page as MHTML' lab.">
         Enables saving pages as MHTML: a single text file containing HTML and all sub-resources.
       </message>
-      
+
       <!-- Flag and values for MHTML Geenrator options lab. -->
       <message name="IDS_FLAGS_MHTML_GENERATOR_OPTION_NAME" desc="Name of the 'MHTML Generator Options' lab.">
         MHTML Generation Option
@@ -11267,15 +11267,25 @@ The following application will be launched if you accept this request:
       </if>
 
       <!-- General app failure messages -->
-      <message name="IDS_COULDNT_OPEN_PROFILE_ERROR" desc="Error displayed on startup when the profile can not be opened correctly due to problems reading or writing files in it">
+      <message name="IDS_COULDNT_OPEN_PROFILE_ERROR" desc="Error displayed on startup when the profile can not be opened correctly due to problems reading or writing files in it.">
 Your profile could not be opened correctly.
 
 Some features may be unavailable.  Please check that the profile exists and you have permission to read and write its contents.
       </message>
-      <message name="IDS_REFUSE_TO_RUN_AS_ROOT" desc="Short error message displayed in an error dialog on startup if the user tries to run Chrome as root">
+      <message name="IDS_COULDNT_OPEN_SPECIFIED_PROFILE_ERROR" desc="Error displayed on startup failure, when the profile specified in the --profile-directory switch cannot be opened correctly.">
+Cannot start Chrome because the specified profile could not be opened correctly.
+
+Please check that the profile exists and you have permission to read and write its contents.
+      </message>
+      <message name="IDS_COULDNT_OPEN_ANY_PROFILE_ERROR" desc="Error displayed on startup failure, when none of the existing profiles can be opened correctly.">

[brettw, 2016/06/14 00:02:07]

I think I would not bother adding these 2 new messages and just re-use the
IDS_COULDNT_OPEN_PROFILE_ERROR message for all of the related errors. The
difference between these two cases to an end-user is not actionable and it just
adds more messages we need to maintain.

[WC Leung, 2016/06/15 17:44:08]

I think we still need to add one string if two strings are too much.
IDS_COULDNT_OPEN_PROFILE_ERROR does not carry the notion that Chromium cannot
start (I am using it in 2061593002). Here we need a string that clearly state
that Chromium cannot start.

+Cannot start Chrome because all of the stored profiles could not be opened correctly.
+
+Please check that the profile exists and you have permission to read and write its contents.
+      </message>
+      <message name="IDS_REFUSE_TO_RUN_AS_ROOT" desc="Short error message displayed in an error dialog on startup if the user tries to run Chrome as root.">
         <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> can not be run as root.
       </message>
-      <message name="IDS_REFUSE_TO_RUN_AS_ROOT_2" desc="Detailed message in the error dialog when the user tries to start Chrome as root">
+      <message name="IDS_REFUSE_TO_RUN_AS_ROOT_2" desc="Detailed message in the error dialog when the user tries to start Chrome as root.">
         Please start <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> as a normal user. To run as root, you must specify an alternate --user-data-dir for storage of profile information.
       </message>
       <if expr="is_win">