[tor-relays] relay memory leak?

[Fran]

Hey,

new non-exit relay, Debian 11, tor 0.4.7.8-1~d11.bullseye+1, ~ 1 week 
old (-> no guard)

KVM VM with atm 4 cores, host passthrough AMD EPYC (-> AES HW accel.).

As can be seen at the attached screenshots memory consumption is 
irritating as well as the quite high CPU load.

All was fine when it had ~100 Mbit/s but then onion skins exploded (110 
per second -> up to 4k per second) as well as CPU and memory.


Tor complains:

 > Your computer is too slow to handle this many circuit creation 
requests! Please consider using the MaxAdvertisedBandwidth config option 
or choosing a more restricted exit policy.


And from time to time memory killer takes action


torrc is pretty basic:

Nickname 123
ContactInfo 123
RunAsDaemon 1
Log notice syslog
RelayBandwidthRate 2X MBytes
RelayBandwidthBurst 2X MBytes
SocksPort 0
ControlSocket 0
CookieAuthentication 0
AvoidDiskWrites 1
Address  xxxx
OutboundBindAddress yyyy
ORPort xxxx:yyy
Address  [zzzz]
OutboundBindAddress [zzz]
ORPort [zzz]:xxx
MetricsPort hhhh:sss
MetricsPortPolicy accept fffffff
DirPort yy
Sandbox 1
NoExec 1
CellStatistics 1
ExtraInfoStatistics 1
ConnDirectionStatistics 1
EntryStatistics 1
ExitPortStatistics 1
HiddenServiceStatistics 1


Ideas/suggestions (apart from limiting BW) to fix this?

Thanks

fran
-------------- next part --------------
A non-text attachment was scrubbed...
Name: onion-skins.png
Type: image/png
Size: 79965 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20220722/1089b505/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tor-cpu-memory-traffic.png
Type: image/png
Size: 144942 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20220722/1089b505/attachment-0003.png>