Here we go: Tor v0.4.8.18-1~d11.bullseye+1 running on Debian Bullseye 13.1.
Todays’ log:
Nov 11 22:33:06.033 [notice] Tor 0.4.8.18 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.3.1, Liblzma 5.8.1, Libzstd 1.5.7 and Glibc 2.41 as libc.
…
Nov 12 19:01:16.000 [notice] We’re low on memory (cell queues total alloc: 528 buffer total alloc: 184320, tor compress total alloc: 597260954 (zlib: 395520, zstd: 11141352, lzma: 585723954), rendezvous cache total alloc: 0). Killing circuits withover-long queues. (This behavior is controlled by MaxMemInQueues.)
Nov 12 19:01:16.000 [notice] Removed 184848 bytes by killing 1 circuits; 0 circuits remain alive. Also killed 4 non-linked directory connections. Killed 0 edge connections
Tor killed connections and released “just” 180K, while compression buffers are 670M. I can imagine how many connections one can handle with that buffer 
# /bin/ps -C tor -o pid,comm,vsz,rss,cmd
PID COMMAND VSZ RSS CMD
2987156 tor 968648 571364 /usr/bin/tor ...
I suspect that due to intensive attempts to free memory, other Tor bugs pop up, see also another my post:
Nov 12 10:27:14.000 [warn] connection_edge_about_to_close(): Bug: (Harmless.) Edge connection (marked at ../src/core/or/circuitlist.c:2716)
hasn't sent end yet? (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] tor_bug_occurred_(): Bug: ../src/core/or/connection_edge.c:1086: connection_edge_about_to_close: This line should not have been reached. (Future instances of this warning will be silenced.) (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: Tor 0.4.8.18: Line unexpectedly reached at connection_edge_about_to_close at ../src/core/or/connection_edge.c:1086. Stack trace: (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(log_backtrace_impl+0x57) [0x560594ec7197] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(tor_bug_occurred_+0x16b) [0x560594ed22fb] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(connection_exit_about_to_close+0x1d) [0x560594f7b48d] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(+0x6f65d) [0x560594e4a65d] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(+0x6fd6b) [0x560594e4ad6b] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(+0x21937) [0x7f6b1a1fb937] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /lib/x86_64-linux-gnu/libevent-2.1.so.7(event_base_loop+0x49f) [0x7f6b1a1fc13f] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(do_main_loop+0x101) [0x560594e4c761] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(tor_run_main+0x1e5) [0x560594e48005] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(tor_main+0x49) [0x560594e44319] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(main+0x19) [0x560594e43ef9] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7f6b19a26ca8] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f6b19a26d65] (on Tor 0.4.8.18 )
Nov 12 10:27:14.000 [warn] Bug: /usr/bin/tor(_start+0x2a) [0x560594e43f4a] (on Tor 0.4.8.18 )
Nov 12 10:27:15.000 [notice] We're low on memory (cell queues total alloc: 528 buffer total alloc: 0, tor compress total alloc: 510386111 (zlib: 0, zstd: 22282704, lzma: 488103295), rendezvous cache total alloc: 0). Killing circuits withover-long queues. (This behavior is control: