[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #7087 [Tor]: memory leaks in new channel code



#7087: memory leaks in new channel code
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:                    
     Type:  defect     |         Status:  new               
 Priority:  normal     |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor        |        Version:                    
 Keywords:  tor-relay  |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by andrea):

 I have a repro for this; I've just attached valgrind output, edited to
 remove non-channel/cmux-related warnings and sort the detect leaks into
 functionally related groups.  To summarize, there are three basic groups
 of a definite leak and a matching number of plainly related indirect leaks
 [1].  The first group flows through channel_tls_handle_incoming() (six
 channels appear to have leaked) and the second leaks in identical fashion
 but via channel_tls_connect() for seven channels.  The third functional
 group consists of a single leaked channel_listener_t.

 [1] All share a common stack trace prefix, except for one set of
 indirectly leaked blocks each with chanid_circid_muxinfo_map_HT_GROW()
 instead, apparently from the first circuit attached to each of the
 affected channels.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7087#comment:2>
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