Bug 193844

Summary: Move logic from ChildProcess::setApplicationIsDaemon to NetworkProcess::initializeProcess
Product: WebKit Reporter: Alex Christensen <achristensen>
Component: New BugsAssignee: Alex Christensen <achristensen>
Status: RESOLVED FIXED    
Severity: Normal CC: aestes, ap, bfulgham, pvollan, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Alex Christensen
Reported 2019-01-25 13:41:23 PST
Move logic from ChildProcess::setApplicationIsDaemon to NetworkProcess::initializeProcess
Attachments
Patch (3.53 KB, patch)
2019-01-25 13:42 PST, Alex Christensen
no flags
Patch (4.87 KB, patch)
2019-01-25 15:40 PST, Alex Christensen
no flags
Alex Christensen
Comment 1 2019-01-25 13:42:07 PST
Andy Estes
Comment 2 2019-01-25 15:08:48 PST
Comment on attachment 360155 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=360155&action=review > Source/WebKit/NetworkProcess/mac/NetworkProcessMac.mm:50 > +extern "C" OSStatus SetApplicationIsDaemon(Boolean isDaemon); This should be in an SPI header.
Alex Christensen
Comment 3 2019-01-25 15:40:27 PST
Alex Christensen
Comment 4 2019-01-25 15:41:44 PST
Radar WebKit Bug Importer
Comment 5 2019-01-25 15:42:27 PST
Alexey Proskuryakov
Comment 6 2019-01-26 00:31:30 PST
Comment on attachment 360178 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=360178&action=review > Source/WebKit/ChangeLog:8 > + This simplifies ChildProcess and removes NetworkProcess-specific code from this generic abstraction. The radar quoted as explanation of why this is needed in NetworkProcess is ancient. I’m guessing that we either need it in all child processes, or in none. Is it still doing anything useful in NetworkProcess? Does it even have a WindowServer connection before this call?
Note You need to log in before you can comment on or make changes to this bug.