Chrome Version: 59.0.3035.0
OS: macOS 10.12.3
What steps will reproduce the problem?
(1) --enable-features=NativeNotifications
(2) Generate a persistent notification via https://tests.peter.sh/notification-generator/#actions=1;;requireInteraction=true
(3) `ps ax | grep AlertNotification`
(4) `kill -ILL <pid>` of the AlertNotificationService
(5) Go to chrome://crashes, do not see a crash report
What is the expected result?
A crash report should be generated by Crashpad.
What happens instead?
No crash report is generated by Crashpad.
This bug has a couple of steps:
1) Determine why launchd does not use the exception port of the connection creator for the XPCService, when the service is an Application-domain one
2) Investigate whether launchd is capable of making #1 happen
3) Get the AlertNotificationService to use Crashpad
4) Make sure that AlertNotificationService is dump_syms'd and symupload'd.
Comment 1 by bugdroid1@chromium.org
, Mar 9 2017