xserver-multidpi/hw
Jeremy Huddleston 3505e1faad XQuartz: Detect FatalErrors on startup to prevent tight crash loops
If a FatalError occurs before the server finishes launching, it will
not have drained the launchd-owned DISPLAY socket, so launchd will
just relaunch it.  This can cause the server to crash in a tight loop
which will spam the user with CrashReporter windows that claim focus on
appearance.

This allows users stuck in this loop to "deal" with the problem without
popping up a crash report every 10 seconds.

Signed-off-by: Jeremy Huddleston <jeremyhu@apple.com>
2012-03-24 01:07:05 -07:00
..
dmx os: Pass the FatalError message to OsVendorFatalError 2012-03-24 01:07:05 -07:00
kdrive os: Pass the FatalError message to OsVendorFatalError 2012-03-24 01:07:05 -07:00
vfb os: Pass the FatalError message to OsVendorFatalError 2012-03-24 01:07:05 -07:00
xfree86 os: Pass the FatalError message to OsVendorFatalError 2012-03-24 01:07:05 -07:00
xnest os: Pass the FatalError message to OsVendorFatalError 2012-03-24 01:07:05 -07:00
xquartz XQuartz: Detect FatalErrors on startup to prevent tight crash loops 2012-03-24 01:07:05 -07:00
xwin os: Pass the FatalError message to OsVendorFatalError 2012-03-24 01:07:05 -07:00
Makefile.am Catch errors in recursive relink targets 2010-03-22 00:45:57 -05:00