[tor-bugs] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

[Tor Bug Tracker & Wiki]

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x000055ed468598d0
--------------------------+---------------------------------
 Reporter:  cypherpunks   |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.3.5-rc
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+---------------------------------

Comment (by starlight):

 Another diagnostic avenue (if you feel up to hacking on it--not for the
 faint-of-heart) is to trace glibc memory.  This will produce insanely huge
 log files so  only attempt it if you have at least 100GB available. . .1TB
 is more like it.

 Referring to the documentation at http://man7.org/linux/man-
 pages/man3/mtrace.3.html compile a memory-trace tor executable and add
 MALLOC_TRACE=/???/mtrace.out to the environment of the daemon.
 Once the daemon is up grab a copy of the memory map from
 /proc/<tor_pid>/maps.

 When it fails, one analyzes the log using the process memory map and the
 mtrace.pl perl script or an alternate.

 Not worth the trouble unless demonstrably usable line-number debug
 information is in place for for the tor images and the system libraries.

 WARNING:  the above constitutes a ''lot'' of trouble and work -- major
 effort

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26311#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online