aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/tor.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-12-08 16:35:33 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-12-08 16:35:33 -0400
commit6a3131228c81824a82514aa9c6e21cd4f83ce696 (patch)
treebb584c15ed7eebcbfc0caac6f0ca36e11f3fca4b /doc/todo/tor.mdwn
parent97297980d1031b3c35e98e605a6c0034815846dd (diff)
we have a memory leak
Diffstat (limited to 'doc/todo/tor.mdwn')
-rw-r--r--doc/todo/tor.mdwn9
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/todo/tor.mdwn b/doc/todo/tor.mdwn
index b262c793c..ca3e8f19a 100644
--- a/doc/todo/tor.mdwn
+++ b/doc/todo/tor.mdwn
@@ -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