Summary: | [WK2][LEAK] Cross reference between WebContext and WebProcessProxy | ||
---|---|---|---|
Product: | WebKit | Reporter: | Kangil Han <kangil.han> |
Component: | WebKit2 | Assignee: | Kangil Han <kangil.han> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | ap, cgarcia, gyuyoung.kim, ryuan.choi, sam |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Other | ||
OS: | Linux | ||
Bug Depends on: | |||
Bug Blocks: | 94697 |
Description
Kangil Han
2012-08-22 23:57:20 PDT
The loop is broken by WebContext::disconnectProcess(). (In reply to comment #1) > The loop is broken by WebContext::disconnectProcess(). Yes and before it we have 'WebProcessProxy::disconnect'. However, the problem I described is, WebProcessProxy couldn't trigger WebContext::disconnectProcess() on normal exit because it has no interface with it. WebProcessProxy::disconnect() is executed on a message from WebProcess (ShouldTerminate). (In reply to comment #3) > WebProcessProxy::disconnect() is executed on a message from WebProcess (ShouldTerminate). Yes and before it there is 'ChildProcess::terminationTimerFired()'. But, it seems not to be triggered on normal exit. It seems we don't have any IPC connection even if it is triggered because UI process already quit connection. It's possible that it's not called on exit. Why do you want to spend extra time on cleanup during UI process exit? (In reply to comment #5) > It's possible that it's not called on exit. Why do you want to spend extra time on cleanup during UI process exit? I am interested in cleaning WebContext on exit. What I have described in the bug is that I think we don't have any WK2 interface for it. Therefore, I would like to discuss for this and do fix if you would like it. :-) That's probably worth discussing on webkit-dev first. We've said "no" to similar efforts before, since that's a lot of work and long-term liability for marginal benefit. |