summaryrefslogtreecommitdiff
path: root/doc/bugs/S3_memory_leaks.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-10-07 23:10:28 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-10-07 23:10:28 -0400
commit7057ce97cce7622051815cf8dd6c8ddd5ac0f62c (patch)
treecf24898ac57348f49f316b77a85e8ac16fad8cf0 /doc/bugs/S3_memory_leaks.mdwn
parent3872945f876941d75d2b188546f9dc4b305cda8c (diff)
update; branch
Diffstat (limited to 'doc/bugs/S3_memory_leaks.mdwn')
-rw-r--r--doc/bugs/S3_memory_leaks.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/bugs/S3_memory_leaks.mdwn b/doc/bugs/S3_memory_leaks.mdwn
index f612de396..2f72b09ac 100644
--- a/doc/bugs/S3_memory_leaks.mdwn
+++ b/doc/bugs/S3_memory_leaks.mdwn
@@ -8,3 +8,7 @@ file size.
The author of hS3 is aware of the problem, and working on it. I think I
have identified the root cause of the buffering; it's done by hS3 so it can
resend the data if S3 sends it a 307 redirect. --[[Joey]]
+
+At least the send leak should be fixed by the patch in the s3-memory-leak
+branch in git. That needs a patch to hS3, which I have sent to its author.
+--[[Joey]]