[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #26933 [Core Tor/Tor]: Minor memleak in HSv3 configuration
#26933: Minor memleak in HSv3 configuration
--------------------------------------+------------------------------------
Reporter: asn | Owner: nickm
Type: defect | Status: accepted
Priority: Medium | Milestone: Tor: 0.3.5.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: easy memleak hsv3 tor-hs | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+------------------------------------
Comment (by nickm):
oh wait, I was thinking of escaped(). But that's one we're calling here,
so this still probably isn't a real leak. (What escaped() does is to free
its last-returned value each time it is called; escaped(NULL) is supposed
to free the last-returned value without creating a new one.)
Nonetheless, I am not sure how this is happening. The tor_free_all()
function calls escaped(NULL), which is supposed to free this memory.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26933#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs