mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

we have a memory leak

Browse source
This commit is contained in:
Joey Hess 2016-12-08 16:35:33 -04:00
parent d8f1a0d95c
commit b8fea9f08d
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/todo/tor.mdwn
View file

@ -4,8 +4,13 @@ Mostly working!
Current todo list:
* copy --to peer seems to make the remotedaemon buffer the content in
memory, more than I'd expect. Check if this is a memory leak..
* copy --to peer of a 100 mb file causes the memory of the remotedaemon
to creep up from 40 mb to 136 mb. Once the transfer is done, the
remotedaemon continues using all that memory. Memory leak. Profile it.
(The sending process creeps up some initially, but stops at 45 mb used.
That could just be buffering.)
(copy --from peer does not leak on either end; the remotedaemon uses 34
mb and the receiver 44 mb.)
* When a transfer can't be done because another transfer of the same
object is already in progress, the message about this is output by the
remotedaemon --debug, but not forwarded to the peer, which shows