Add temporary DumpWithoutCrashing to understand why the filesystem URL origin checks are failing in

content/browser/child_process_security_policy_impl.cc

Index: content/browser/child_process_security_policy_impl.cc
diff --git a/content/browser/child_process_security_policy_impl.cc b/content/browser/child_process_security_policy_impl.cc
index a7b4d8854ed4893e2e40bdd26fda909b90c3f31f..66a4c3add715ddab6d56d994ed22f6d496124368 100644
--- a/content/browser/child_process_security_policy_impl.cc
+++ b/content/browser/child_process_security_policy_impl.cc
@@ -8,6 +8,7 @@
 #include <utility>
 
 #include "base/command_line.h"
+#include "base/debug/dump_without_crashing.h"
 #include "base/files/file_path.h"
 #include "base/logging.h"
 #include "base/macros.h"
@@ -801,6 +802,8 @@ bool ChildProcessSecurityPolicyImpl::HasPermissionsForFileSystemFile(
   // API either.
   if (!CanCommitURL(child_id, filesystem_url.origin())) {
     UMA_HISTOGRAM_BOOLEAN("FileSystem.OriginFailedCanCommitURL", true);
+    // TODO(nick): Temporary instrumentation for https://crbug.com/654479.
+    base::debug::DumpWithoutCrashing();

[nasko, 2016/10/10 21:45:09]

Should we capture the filesystem_url contents explicitly to ensure they are in
the dump? Or do we care mostly about the stack trace?

     return false;
   }