[tor-commits] [torspec/master] control-spec: Clarify that the 16MB buffer limit went away in 2007

nickm at torproject.org nickm at torproject.org
Thu Jun 29 14:40:56 UTC 2017


commit b38e7ef011ffca4967e53bc461cc8af98ff78917
Author: Nick Mathewson <nickm at torproject.org>
Date:   Thu Jun 29 10:39:44 2017 -0400

    control-spec: Clarify that the 16MB buffer limit went away in 2007
    
    Closes ticket 22742.
---
 control-spec.txt | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/control-spec.txt b/control-spec.txt
index aead150..275221c 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -3102,8 +3102,13 @@
 
 5.2. Don't let the buffer get too big.
 
-  If you ask for lots of events, and 16MB of them queue up on the buffer,
-  the Tor process will close the socket.
+  With old versions of Tor (before 0.2.0.16-alpha), if you ask for
+  lots of events, and 16MB of them queue up on the buffer, the Tor
+  process will close the socket.
+
+  Newer Tor versions do not have this 16 MB buffer limit. However,
+  if you leave huge numbers of events unread, Tor may still run out
+  of memory, so you should still be careful about buffer size.
 
 5.3. Backward compatibility with v0 control protocol.
 



More information about the tor-commits mailing list