Identify the hung thread using the Wait Chain Traversal API

chrome/chrome_watcher/chrome_watcher_main.cc

Index: chrome/chrome_watcher/chrome_watcher_main.cc
diff --git a/chrome/chrome_watcher/chrome_watcher_main.cc b/chrome/chrome_watcher/chrome_watcher_main.cc
index 95ead7765eb414e75cccb197379dcd42485d7e81..8e0007945cb7b157c66dcf90abacd2bd4210f520 100644
--- a/chrome/chrome_watcher/chrome_watcher_main.cc
+++ b/chrome/chrome_watcher/chrome_watcher_main.cc
@@ -224,11 +224,9 @@ extern "C" int WatcherMain(const base::char16* registry_path,
                                                 browser_data_directory);
 
 #if BUILDFLAG(ENABLE_KASKO_HANG_REPORTS)
-  // Only activate hang reports for the canary channel. For testing purposes,
-  // Chrome instances with no channels will also report hangs.
+  // Only activate hang reports for the canary channel.
   if (launched_kasko &&
-      (base::StringPiece16(channel_name) == L"" ||
-       base::StringPiece16(channel_name) == installer::kChromeChannelCanary)) {
+      base::StringPiece16(channel_name) == installer::kChromeChannelCanary) {
     on_hung_callback = base::Bind(&DumpHungProcess, main_thread_id,
                                   channel_name, L"hung-process");
   }