Memory leek with Trint checked with valgrind

Hello Rooters

Please, Let’s me understand leek memory with Root!

when we run root with vagrind , non leek is reported
but when i try to use TRint , a i have 180 lost reccord in this simple example

#include "TRint.h"
int main(int argc, char **argv) {

  TRint* theApp = new TRint("GRU", &argc, argv, NULL, 0);
  delete (theApp);


that it’s compiled with this command :
gcc test.C -pthread -m32 -I/usr/global/root/root5.16//include -L/usr/global/root/root5.16//lib -lCore -lCint -lRIO -lNet -lHist -lGraf -lGraf3d -lGpad -lTree -lRint -lPostscript -lMatrix -lPhysics -lGui -pthread -lm -ldl -rdynamic -o test

Thanks for you help

So far, most (if not all) these leaks are things that we (for now) intentionally do not delete at the end of the process for the sake of not slowing down the termination of the process (aka they are not real leaks, just global state that is not cleaned up entirely). We intend on improving this in the future to help with using memory leak checkers like valgrind.