Fix for memory trampling in onion local mapping pool.
I attempted to open the PR against the master branch of this repository, but it seemed to swallow that change and open it against the master of my own:
https://gitlab.torproject.org/anonhelper/torsocks/-/merge_requests/1
There was no option to mark that PR as confidential, but the visibility of my account is set to limited overall in this Gitlab instance.
It's unclear how much of a security risk this actually presents, it would take an amazing amount of heap grooming in a client to possibly lead to more than corruption.
In any case it is a good excuse to exercise the confidential pathways.
The commit is signed, if possible can it be rebased/cherry-picked onto master?