You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by sh...@apache.org on 2015/04/28 21:37:55 UTC
trafficserver git commit: TS-3536: Fix memory leak in post
processing. This closes #187
Repository: trafficserver
Updated Branches:
refs/heads/master 0a51ce2f6 -> 4561001e2
TS-3536: Fix memory leak in post processing.
This closes #187
Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/4561001e
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/4561001e
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/4561001e
Branch: refs/heads/master
Commit: 4561001e20adf05e17eba810e25a0036d627b83e
Parents: 0a51ce2
Author: Feifei Cai <ff...@yahoo-inc.com>
Authored: Tue Apr 28 14:36:11 2015 -0500
Committer: shinrich <sh...@yahoo-inc.com>
Committed: Tue Apr 28 14:36:11 2015 -0500
----------------------------------------------------------------------
CHANGES | 2 ++
proxy/http/HttpSM.cc | 1 +
2 files changed, 3 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/4561001e/CHANGES
----------------------------------------------------------------------
diff --git a/CHANGES b/CHANGES
index 4790441..eb6b45e 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,6 +1,8 @@
-*- coding: utf-8 -*-
Changes with Apache Traffic Server 6.0.0
+ *) [TS-3536] Fix memory leak in post processing.
+
*) [TS-3561] Call TSMutexDestroy in a couple of plugins, now that its
available.
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/4561001e/proxy/http/HttpSM.cc
----------------------------------------------------------------------
diff --git a/proxy/http/HttpSM.cc b/proxy/http/HttpSM.cc
index 0e8918a..47c681f 100644
--- a/proxy/http/HttpSM.cc
+++ b/proxy/http/HttpSM.cc
@@ -5078,6 +5078,7 @@ HttpSM::handle_post_failure()
t_state.current.server->keep_alive = HTTP_NO_KEEPALIVE;
if (server_buffer_reader->read_avail() > 0) {
+ tunnel.deallocate_buffers();
tunnel.reset();
// There's data from the server so try to read the header
setup_server_read_response_header();