RestrictCookieManager: add some crash keys to debug renderer kills on Android

What's strange is that in-NetworkService BadMessage catchers on desktop
doesn't seem to see this check failing.

Bug: 983090
Change-Id: I4ddd91909635fb978c7e0675ed48a567de8f0bbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713391Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#679939}

services/network/restricted_cookie_manager.cc

@@ -10,6 +10,7 @@
 
 #include "base/bind.h"
 #include "base/compiler_specific.h"  // for FALLTHROUGH;
+#include "base/debug/crash_logging.h"
 #include "base/memory/weak_ptr.h"
 #include "base/sequenced_task_runner.h"
 #include "base/strings/string_util.h"
@@ -443,6 +444,20 @@ bool RestrictedCookieManager::ValidateAccessToCookiesAt(const GURL& url) {
   if (origin_.IsSameOriginWith(url::Origin::Create(url)))
     return true;
 
+  // TODO(https://crbug.com/983090): Remove the crash keys once fixed.
+  static base::debug::CrashKeyString* bound_origin =
+      base::debug::AllocateCrashKeyString(
+          "restricted_cookie_manager_bound_origin",
+          base::debug::CrashKeySize::Size256);
+  base::debug::SetCrashKeyString(bound_origin, origin_.GetDebugString());
+
+  static base::debug::CrashKeyString* url_origin =
+      base::debug::AllocateCrashKeyString(
+          "restricted_cookie_manager_url_origin",
+          base::debug::CrashKeySize::Size256);
+  base::debug::SetCrashKeyString(url_origin,
+                                 url::Origin::Create(url).GetDebugString());
+
   mojo::ReportBadMessage("Incorrect url origin");
   return false;
 }