tor package: reconsider --with-openbsd-malloc

[ng0 <contact.ng0@cryptolab.net>]

A while back I introduced the hardening flags to the tor package.

TGR wrote about an additional option, --with-openbsd-malloc, which can
be used[0].
Now I know that some (or only one?) of the settings I introduced will be
dropped again (after a long time) in one of the next releases of tor.

My "tor" process on clients in htop displays a constant 20.0T for the
virtual size, a resident size of around 525M, and in fact only 464(M?)
of the 20.0T are sharable.

If we would compile tor with openbsd malloc, we would have more cpu
load but apparently the process would be easier on the RAM. I would be
surprised if anyone is running a relay (non-exit, exit) with GuixSD or tor from Guix
already, but if you do and you can speak out about it without facing issues
for making it publicly known, your advice is welcome.
You can also contact me offlist, my keys can be found on
https://people.pragmatique.xyz/ng0/ or on the sks keyservers.

If no one replies within a sufficient timeframe of 4 weeks, I will go
ahead and create a patch for what TGR adviced back then.

Of course I'm also interested in the opion of those who just use it as a
client.

0: https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02306.html