Since the WebContent process is no longer using the NSApplication run loop, the NSApp object is no longer guaranteed to be non-nil. We are currently calling [NSApplication sharedApplication] in WebProcess::platformInitializeWebProcess which will set NSApp, but we will possibly remove this call in the future. We should identify where we reference NSApp in the WebContent process, and determine how each case should be handled when we are using NSRunLoop.
<rdar://problem/37287247>