diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-04-19 16:03:27 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-04-19 16:03:27 -0400 |
| commit | 030c7a056b0795adf037464d608da5170638f4ac (patch) | |
| tree | 8d26073310c9664a0f49950339234e8c8bb2a3ad /doc/bugs/S3_memory_leaks.mdwn | |
| parent | 5985acdfad8a6791f0b2fc54a1e116cee9c12479 (diff) | |
update
Diffstat (limited to 'doc/bugs/S3_memory_leaks.mdwn')
| -rw-r--r-- | doc/bugs/S3_memory_leaks.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/S3_memory_leaks.mdwn b/doc/bugs/S3_memory_leaks.mdwn new file mode 100644 index 000000000..d7cae2933 --- /dev/null +++ b/doc/bugs/S3_memory_leaks.mdwn @@ -0,0 +1,13 @@ +S3 has two memory leaks. + +One only occurs with encryption. It was was fixed for bup, but +not yet for S3, in 5985acdfad8a6791f0b2fc54a1e116cee9c12479. + +The other occurs independant of encryption use. Copying a 100 mb +file to S3 causes an immediate sharp memory spike to 119 mb. +Copying the file back from S3 causes a slow memory increase toward 119 mb. +It's likely that this memory is used by the hS3 library, if it does not +construct the message to Amazon lazily. (And it may not be possible to +construct it lazily, if it includes checksum headers..) I have +emailed the hS3 author about this. +--[[Joey]] |