Always set bad_message_reason when logging bad message dumps

The crash key was accidentally left unset when bad message dumps
were moved to the IO thread. This fixes that.

BUG=680542
R=creis@chromium.org

Review-Url: https://codereview.chromium.org/2629773002
Cr-Commit-Position: refs/heads/master@{#443440}

content/browser/bad_message.cc

@@ -33,8 +33,6 @@ void ReceivedBadMessageOnUIThread(int render_process_id,
   if (!host)
     return;
 
-  LogBadMessage(reason);
-
   // A dump has already been generated by the caller. Don't generate another.
   host->ShutdownForBadMessage(
       RenderProcessHost::CrashReportMode::NO_CRASH_DUMP);
@@ -49,8 +47,9 @@ void ReceivedBadMessage(RenderProcessHost* host, BadMessageReason reason) {
 }
 
 void ReceivedBadMessage(int render_process_id, BadMessageReason reason) {
-  // We generate a crash dump here since generating one after posting the UI
-  // thread is mostly useless.
+  // We generate a crash dump here since generating one after posting to the UI
+  // thread is less useful.
+  LogBadMessage(reason);
   base::debug::DumpWithoutCrashing();
 
   if (!BrowserThread::CurrentlyOn(BrowserThread::UI)) {