diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-04-21 11:06:29 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-04-21 11:06:29 -0400 |
| commit | 2467c567713321b061c3daf92df39d4e35226c7b (patch) | |
| tree | 38ea4f75a533d32e1f0a74648ee3940f3dbb8315 /doc/bugs | |
| parent | 45bdb2d4136f2faf61a3fde63477ad5d935583b1 (diff) | |
update on S3 memory leaks
The remaining leaks are in hS3. The leak with encryption was worked around
by the use of the temp file. (And was probably originally caused by
gpgCipherHandle sparking a thread which kept a reference to the start
of the byte string.)
Diffstat (limited to 'doc/bugs')
| -rw-r--r-- | doc/bugs/S3_memory_leaks.mdwn | 15 |
1 files changed, 3 insertions, 12 deletions
diff --git a/doc/bugs/S3_memory_leaks.mdwn b/doc/bugs/S3_memory_leaks.mdwn index bfb3e1ec5..d8b10b075 100644 --- a/doc/bugs/S3_memory_leaks.mdwn +++ b/doc/bugs/S3_memory_leaks.mdwn @@ -1,17 +1,8 @@ S3 has memory leaks -## with encryption +Sending a file to S3 causes a slow memory increase toward the file size. -One only occurs with encryption. It was was fixed for bup, but -not yet for S3, in 5985acdfad8a6791f0b2fc54a1e116cee9c12479. -(The fix I used for bup doesn't seem to work with S3.) - -## always - -Copying the file back from S3 causes a slow memory increase toward 119 mb. +Copying the file back from S3 causes a slow memory increase toward the +file size. The author of hS3 is aware of the problem, and working on it. - -## fixed - -memory leak while uploading content to S3 |