mac: Crash on uncaught Objective-C exceptions routed to NSApplication

content/app/mac/mac_init.mm

Index: content/app/mac/mac_init.mm
diff --git a/content/app/mac/mac_init.mm b/content/app/mac/mac_init.mm
index 042663c76743330e0ee20cd3c0108ecba1e7dd56..129757b652753812c5e493feb2ea694bce9b6de0 100644
--- a/content/app/mac/mac_init.mm
+++ b/content/app/mac/mac_init.mm
@@ -12,7 +12,16 @@
 
 void InitializeMac() {
   [[NSUserDefaults standardUserDefaults] registerDefaults:@{
+      // Exceptions routed to -[NSApplication reportException:] should crash
+      // immediately, as opposed being swallowed or presenting UI that gives the
+      // user a choice in the matter.
+      @"NSApplicationCrashOnExceptions": @YES,
+
+      // Prevent Cocoa from turning command-line arguments into
+      // |-application:openFiles:|, because they are handled directly.  @"NO"
+      // looks like a mistake, but the value really is supposed to be a string.

[Mark Mentovai, 2016/07/01 21:07:22]

I double-checked this comment and it’s still true.

       @"NSTreatUnknownArgumentsAsOpen": @"NO",
+
       // CoreAnimation has poor performance and CoreAnimation and
       // non-CoreAnimation exhibit window flickering when layers are not hosted
       // in the window server, which is the default when not not using the