aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/S3_memory_leaks.mdwn
Commit message (Collapse)AuthorAge
* remove old closed bugs and todo items to speed up wiki updates and reduce sizeGravatar Joey Hess2016-04-19
| | | | | | | | | Remove closed bugs and todos that were last edited or commented before Q3 2015. Command line used: for f in $(grep -l '\[\[done\]\]' -- *.mdwn); do d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=09-09-2015 --pretty=oneline -- "$f")" -a -z "$(git log --since=09-09-2015 --pretty=oneline -- "$d")" ]; then git rm -- "$f"; git rm -rf "$d"; fi; done for f in $(grep -l '|done\]\]' -- *.mdwn); do d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=09-09-2015 --pretty=oneline -- "$f")" -a -z "$(git log --since=09-09-2015 --pretty=oneline -- "$d")" ]; then git rm -- "$f"; git rm -rf "$d"; fi; done
* S3: finish converting to aws libraryGravatar Joey Hess2014-08-09
| | | | | | | | | | | | | | Implemented the Retriever. Unfortunately, it is a fileRetriever and not a byteRetriever. It should be possible to convert this to a byteRetiever, but I got stuck: The conduit sink needs to process individual chunks, but a byteRetriever needs to pass a single L.ByteString to its callback for processing. I looked into using unsafeInerlaveIO to build up the bytestring lazily, but the sink is already operating under conduit's inversion of control, and does not run directly in IO anyway. On the plus side, no more memory leak..
* remove dead codeGravatar Joey Hess2014-08-09
|
* bug triage; add new 'confirmed' tagGravatar Joey Hess2014-05-24
|
* update; branchGravatar Joey Hess2012-10-07
|
* root causedGravatar Joey Hess2011-04-21
|
* update on S3 memory leaksGravatar Joey Hess2011-04-21
| | | | | | | 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.)
* fix S3 upload buffering problemGravatar Joey Hess2011-04-21
| | | | Provide file size to new version of hS3.
* updateGravatar Joey Hess2011-04-21
|
* heard from hS3 authorGravatar Joey Hess2011-04-19
|
* update on memory leakGravatar Joey Hess2011-04-19
| | | | | Finished applying to S3 the change that fixed the memory leak in bup, but it didn't seem to help S3.. with encryption it still grows to 2x file size.
* updateGravatar Joey Hess2011-04-19