Memory leak with basic TTree

[CorentinH]

$ dpkg -S /etc/root/valgrind-root.supp
root-lpc: /etc/root/valgrind-root.supp

[Wile_E_Coyote]

Well, that really means that your system is screwed.
First, make sure that you “completely remove” / “purge” (i.e. “remove with any associated configuration files”) all ROOT related packages (e.g., dpkg --list "*root*lpc*"; sudo apt-get purge "*root*lpc*").
Then, delete your current ROOT binaries and build it from scratch again.

[CorentinH]

Oh well, I see … A cleaning is in order then !

For information, with the correct valgrind-root.supp file :

$ valgrind --suppressions=/usr/etc/valgrind-root.supp ./run
 Memcheck, a memory error detector
Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
 Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
 Command: ./2read

HEAP SUMMARY:
  in use at exit: 31,864,446 bytes in 47,714 blocks
  total heap usage: 146,196 allocs, 98,482 frees, 108,158,696 bytes allocated
LEAK SUMMARY:
 definitely lost: 16 bytes in 1 blocks
 indirectly lost: 32 bytes in 1 blocks
 possibly lost: 10,777,804 bytes in 8,686 blocks
 still reachable: 1,834,862 bytes in 15,447 blocks
                     of which reachable via heuristic:
                       stdstring          : 40 bytes in 1 blocks
                       newarray           : 16,640 bytes in 30 blocks
                       multipleinheritance: 14,688 bytes in 2 blocks
  suppressed: 19,251,732 bytes in 23,579 blocks
Rerun with --leak-check=full to see details of leaked memory

 For counts of detected and suppressed errors, rerun with: -v
 ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2048 from 183)

And the output of the command leak-check=full:
leak-check-full.txt (993.8 KB)

[Wile_E_Coyote]

Well, I would do the following:

sudo apt-get purge "*root*lpc*" # remove any ROOT system package
dpkg --list "*root*lpc*" # make sure all are gone

cd /currently/installed/root/build/subdirectory
sudo xargs rm < install_manifest.txt # remove own ROOT binaries

Then, remove the source and build subdirectories to start everything from scratch.
Finally, download and build the new version (if possible, take the most recent available version).
See also: Sourcing root for all users

Last, but not least … note that the ROOT Team provides ready-to-use binary distributions for “Ubuntu 18 / gcc 7.5”, which you just need to download and unpack (see “Download a pre-compiled binary distribution”).

[CorentinH]

Thank you so much for your help !