mac: Send SIGTERM instead of SIGHUP to restart Dock

chrome/browser/mac/dock.mm

Index: chrome/browser/mac/dock.mm
diff --git a/chrome/browser/mac/dock.mm b/chrome/browser/mac/dock.mm
index d3a4e16b575db8c7c5669de56c45619d20ad43ae..de218d73dec9cacc6d6f04587fedd93d0c2a2bb4 100644
--- a/chrome/browser/mac/dock.mm
+++ b/chrome/browser/mac/dock.mm
@@ -123,7 +123,7 @@ CFURLRef _CFURLCreateFromPropertyListRepresentation(
   return app_paths;
 }
 
-// Restart the Dock process by sending it a SIGHUP.
+// Restart the Dock process by sending it a SIGTERM.
 void Restart() {
   // Doing this via launchd using the proper job label is the safest way to
   // handle the restart. Unlike "killall Dock", looking this up via launchd
@@ -133,12 +133,12 @@ void Restart() {
     return;
   }
 
-  // Sending a SIGHUP to the Dock seems to be a more reliable way to get the
+  // Sending a SIGTERM to the Dock seems to be a more reliable way to get the
   // replacement Dock process to read the newly written plist than using the
   // equivalent of "launchctl stop" (even if followed by "launchctl start.")
   // Note that this is a potential race in that pid may no longer be valid or
   // may even have been reused.
-  kill(pid, SIGHUP);
+  kill(pid, SIGTERM);
 }
 
 }  // namespace