| commit | 921777f2b0b5adeb766419ffbf6538d10c819912 | [log] [tgz] |
|---|---|---|
| author | jochen@chromium.org <jochen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Thu Mar 15 10:43:22 2012 |
| committer | jochen@chromium.org <jochen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Thu Mar 15 10:43:22 2012 |
| tree | c7b81951118217e9956a8d0d5744827336d46043 | |
| parent | 21d90b88fd5b2a054e4825e89d104bfe1aadbdde [diff] |
Make sure ports are closed when they're no longer used. It appears to be a common pattern that extensions don't invoke the responseCallback, and so the port objects leak. Register a callback that triggers when the responseCallback is finalized to free up these resources. BUG=114738, 93566 TEST=manual Review URL: http://codereview.chromium.org/9693048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126884 0039d316-1c4b-4281-b951-d872f2087c98