diff options
author | kaznacheev@chromium.org <kaznacheev@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-25 11:57:13 +0000 |
---|---|---|
committer | kaznacheev@chromium.org <kaznacheev@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-07-25 11:57:13 +0000 |
commit | b0ec7c0643c7f84db377db2b8fbe23917088b91c (patch) | |
tree | 1295be4207ae4f3d805ca34f9bffb5ef09115dce /content/browser/renderer_host/render_widget_host_unittest.cc | |
parent | e7bb391d7587b643fa52a713786a881c7c86039c (diff) | |
download | chromium_src-b0ec7c0643c7f84db377db2b8fbe23917088b91c.zip chromium_src-b0ec7c0643c7f84db377db2b8fbe23917088b91c.tar.gz chromium_src-b0ec7c0643c7f84db377db2b8fbe23917088b91c.tar.bz2 |
Revert of [WebSocket] Send a close frame when the renderer process is gone. (https://codereview.chromium.org/390773002/)
Reason for revert:
http://build.chromium.org/p/chromium.memory/builders/Linux%20ASan%20LSan%20Tests%20%282%29/builds/5350
Original issue's description:
> [WebSocket] Send a close frame when the renderer process is gone.
>
> Renderer processes may die without clearing its |WebSocketBridge|s.
> It is helpful to send a close frame with code = 1001 in such a case.
>
> BUG=392534
> R=ricea@chromium.org
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=285557
TBR=ricea@chromium.org,jgraettinger@chromium.org,eroman@chromium.org,mmenke@chromium.org,yhirano@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=392534
Review URL: https://codereview.chromium.org/416333004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285564 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/renderer_host/render_widget_host_unittest.cc')
0 files changed, 0 insertions, 0 deletions