Disable renderer CIG temporarily.

This is to allow time for third party vendors who currently inject
into Chrome renderer processes to update their software.

This will be re-enabled in a future release of Chrome.

BUG=750886

Change-Id: I081a44a39ff499b86d02a637cb56ce4b6ff2c17d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885226Reviewed-by: James Forshaw <forshaw@chromium.org>
Commit-Queue: Will Harris <wfh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#710148}

chrome/browser/chrome_content_browser_client.cc

@@ -659,8 +659,9 @@ const char* const kPredefinedAllowedSocketOrigins[] = {
 // Enables pre-launch Code Integrity Guard (CIG) for Chrome renderers, when
 // running on Windows 10 1511 and above. See
 // https://blogs.windows.com/blog/tag/code-integrity-guard/.
+// Disabled temporarily. See https://crbug.com/750886.
 const base::Feature kRendererCodeIntegrity{"RendererCodeIntegrity",
-                                           base::FEATURE_ENABLED_BY_DEFAULT};
+                                           base::FEATURE_DISABLED_BY_DEFAULT};
 #endif  // defined(OS_WIN) && !defined(COMPONENT_BUILD) &&
         // !defined(ADDRESS_SANITIZER)