[tor-bugs] #5337 [Tor Directory Authority]: Memory fragmentation(?) issues on dirauths

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#5337: Memory fragmentation(?) issues on dirauths
-------------------------------------+--------------------------------------
 Reporter:  Sebastian                |          Owner:                    
     Type:  defect                   |         Status:  new               
 Priority:  major                    |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Directory Authority  |        Version:                    
 Keywords:                           |         Parent:                    
   Points:                           |   Actualpoints:                    
-------------------------------------+--------------------------------------
 I wonder how we can better track down the extremely high memory usage on
 some dirauths. For gabelmoo, I notice that the usage is certainly a lot
 higher than it used to be, and that it seems to grow rapidly with drawn-
 out multiple day "plateau" phases of virtually no increase in memory
 footprint. What are debug mechanisms (beyond our default usage of
 valgrind, which doesn't think there are any leaks) that I might be able to
 use here?

 This is a somewhat big issue for me, as gabelmoo makes the system swap and
 therefore unresponsive, so that I have to restart it frequently

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