Bug 131367

Summary: Add API to let the UI process kill the web process despite not using a network process.
Product: WebKit Reporter: Andreas Kling <kling>
Component: WebKit2Assignee: Andreas Kling <kling>
Status: RESOLVED WONTFIX    
Severity: Normal CC: barraclough, kling
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Andreas Kling
Reported 2014-04-08 10:10:12 PDT
<rdar://problem/16506241>
Attachments
Patch (5.77 KB, patch)
2014-04-08 10:13 PDT, Andreas Kling 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Andreas Kling
Comment 1 2014-04-08 10:13:55 PDT
Created attachment 228849 [details] Patch
Alexey Proskuryakov
Comment 2 2014-04-08 10:36:35 PDT
Comment on attachment 228849 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=228849&action=review > Source/WebKit2/ChangeLog:8 > + There are some cases where we'd want to run a web process with in-process networking, > + but don't need to preserve session state when closing the last page in that process. Can we just destroy WebContext in this case?
Andreas Kling
Comment 3 2014-04-08 10:38:47 PDT
(In reply to comment #2) > (From update of attachment 228849 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=228849&action=review > > > Source/WebKit2/ChangeLog:8 > > + There are some cases where we'd want to run a web process with in-process networking, > > + but don't need to preserve session state when closing the last page in that process. > > Can we just destroy WebContext in this case? Yeah, let's do that instead.
Note You need to log in before you can comment on or make changes to this bug.