RESOLVED WONTFIX 180649
The WebContent process should not establish a window server connection.
https://bugs.webkit.org/show_bug.cgi?id=180649
Summary The WebContent process should not establish a window server connection.
Per Arne Vollan
Reported 2017-12-11 08:10:38 PST
Since the WebContent process does not have windows, communication with the window server should not be needed.
Attachments
Patch (2.73 KB, patch)
2017-12-11 08:13 PST, Per Arne Vollan
no flags
Archive of layout-test-results from ews105 for mac-elcapitan-wk2 (79.16 KB, application/zip)
2017-12-11 08:57 PST, EWS Watchlist
no flags
Patch (1.38 KB, patch)
2017-12-11 11:21 PST, Per Arne Vollan
no flags
Patch (1.36 KB, patch)
2017-12-11 12:08 PST, Per Arne Vollan
no flags
Patch (2.76 KB, patch)
2017-12-11 13:26 PST, Per Arne Vollan
no flags
Patch (5.09 KB, patch)
2017-12-12 09:43 PST, Per Arne Vollan
no flags
Patch (5.32 KB, patch)
2017-12-12 10:18 PST, Per Arne Vollan
no flags
Per Arne Vollan
Comment 1 2017-12-11 08:13:30 PST
EWS Watchlist
Comment 2 2017-12-11 08:57:56 PST
Comment on attachment 328975 [details] Patch Attachment 328975 [details] did not pass mac-wk2-ews (mac-wk2): Output: http://webkit-queues.webkit.org/results/5615506 Number of test failures exceeded the failure limit.
EWS Watchlist
Comment 3 2017-12-11 08:57:58 PST
Created attachment 328980 [details] Archive of layout-test-results from ews105 for mac-elcapitan-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: ews105 Port: mac-elcapitan-wk2 Platform: Mac OS X 10.11.6
Per Arne Vollan
Comment 4 2017-12-11 11:21:17 PST
Per Arne Vollan
Comment 5 2017-12-11 12:08:04 PST
Per Arne Vollan
Comment 6 2017-12-11 13:26:11 PST
Per Arne Vollan
Comment 7 2017-12-12 09:43:46 PST
Per Arne Vollan
Comment 8 2017-12-12 10:13:19 PST
(In reply to Per Arne Vollan from comment #7) > Created attachment 329117 [details] > Patch With this patch, there are no references to window server access in the system log (searching for 'CGSLookupServerRootPort').
Per Arne Vollan
Comment 9 2017-12-12 10:18:44 PST
Sam Weinig
Comment 10 2017-12-12 15:35:45 PST
Comment on attachment 329122 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=329122&action=review > Source/WebCore/platform/mac/ThemeMac.mm:72 > + return nullptr; This should return nil. > Source/WebKit/Shared/mac/ChildProcessMac.mm:217 > void ChildProcess::stopNSAppRunLoop() > { > - ASSERT([NSApp isRunning]); > + if (![NSApp isRunning]) { > + CFRunLoopStop([[NSRunLoop currentRunLoop] getCFRunLoop]); > + return; > + } It feels like this function is not named correctly anymore if it sometimes doesn't stop the NSApp runloop. > Source/WebKit/WebProcess/cocoa/WebProcessCocoa.mm:116 > + return 0; This should return nil.
Per Arne Vollan
Comment 11 2017-12-13 20:08:58 PST
(In reply to Sam Weinig from comment #10) > Comment on attachment 329122 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=329122&action=review > > > Source/WebCore/platform/mac/ThemeMac.mm:72 > > + return nullptr; > > This should return nil. > > > Source/WebKit/Shared/mac/ChildProcessMac.mm:217 > > void ChildProcess::stopNSAppRunLoop() > > { > > - ASSERT([NSApp isRunning]); > > + if (![NSApp isRunning]) { > > + CFRunLoopStop([[NSRunLoop currentRunLoop] getCFRunLoop]); > > + return; > > + } > > It feels like this function is not named correctly anymore if it sometimes > doesn't stop the NSApp runloop. > > > Source/WebKit/WebProcess/cocoa/WebProcessCocoa.mm:116 > > + return 0; > > This should return nil. Thanks for reviewing! I will update the patch.
Brent Fulgham
Comment 12 2018-03-08 12:40:18 PST
Equivalent work was done under other Bugzilla entries. This bug is no longer needed.
Maciej Stachowiak
Comment 13 2020-06-02 01:11:29 PDT
Comment on attachment 329122 [details] Patch Unflagging and obsoleting, since this was resolved as WONTFIX (though actually, I think this is a dupe of something we ended up doing later.
Note You need to log in before you can comment on or make changes to this bug.