| 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: | WebKit2 | Assignee: | Andreas Kling <kling> | ||||
| Status: | RESOLVED WONTFIX | ||||||
| Severity: | Normal | CC: | barraclough, kling | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Andreas Kling
2014-04-08 10:10:12 PDT
Created attachment 228849 [details]
Patch
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? (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. |