[cling] teardown: correctly free frontend and retained JITLink allocations

[aaronj0]

Based on the CppInterOp cling+ASan CI job running tests that create and destroy several interpreters per process, and LSan reports two leaks there:

In JITLink, with the upgrade to LLVM22, EHFrameRegistrationPlugin now pushes a deregistration WrapperFunctionCall into each allocation's FinalizedAllocInfo::DeallocActions vector. Our deallocate retains the code via FinalizedAlloc::release(), which orphans that vector's heap buffer.

For the frontend: ShutDown() leaks Sema/ASTContext through the DisableFree path and hides the pointers with llvm::BuryPointe. Its fixed buffer only holds 16 pointers, so once a process destroys a few interpreters it overflows and LSan starts reporting whole frontends, normally with a single interpreter until process exit would not hit this.

[vgvassilev]

Can you confirm root actually calls the cling interpreter destructor?

[aaronj0]

Can you confirm root actually calls the cling interpreter destructor?

root.exe -l -b -q:

  Breakpoint 1.2, 0x00007ffff0d78870 in cling::Interpreter::~Interpreter() () from
  /home/maximus/ROOT/build-minimal-teardown/lib/libCling.so
  #0  0x00007ffff0d78870 in cling::Interpreter::~Interpreter() () from
  /home/maximus/ROOT/build-minimal-teardown/lib/libCling.so
  #1  0x00007ffff0bf7889 in std::default_delete<cling::Interpreter>::operator() (__ptr=<optimized out>,
  this=<optimized out>) at /usr/include/c++/13/bits/unique_ptr.h:93
  #2  std::unique_ptr<cling::Interpreter, std::default_delete<cling::Interpreter> >::~unique_ptr
  (this=0x5555555ff278, __in_chrg=<optimized out>) at /usr/include/c++/13/bits/unique_ptr.h:404
  #3  TCling::~TCling (this=0x5555555fefe0, __in_chrg=<optimized out>) at
  /home/maximus/ROOT/root-coff-fix/core/metacling/src/TCling.cxx:1694
  #4  0x00007ffff0bf79d1 in TCling::~TCling (this=0x5555555fefe0, __in_chrg=<optimized out>) at
  /home/maximus/ROOT/root-coff-fix/core/metacling/src/TCling.cxx:1694
  #5  0x00007ffff7c8b640 in TROOT::~TROOT (this=0x7ffff7edf720 <ROOT::Internal::GetROOT1()::alloc>,
  __in_chrg=<optimized out>) at /home/maximus/ROOT/root-coff-fix/core/base/src/TROOT.cxx:1172
  #6  0x00007ffff7c8986d in at_exit_of_TROOT () at
  /home/maximus/ROOT/root-coff-fix/core/base/src/TROOT.cxx:377
  #7  0x00007ffff7247a76 in __run_exit_handlers (status=0, listp=<optimized out>,
  run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:108
  #8  0x00007ffff7247bbe in __GI_exit (status=<optimized out>) at ./stdlib/exit.c:138
  #9  0x00007ffff7dab21f in TUnixSystem::Exit(int, bool) () from
  /home/maximus/ROOT/build-minimal-teardown/lib/libCore.so
  #10 0x00007ffff7c28097 in TApplication::Terminate(int) () from
  /home/maximus/ROOT/build-minimal-teardown/lib/libCore.so
  #11 0x00007ffff7fa2463 in TRint::Run(bool) () from
  /home/maximus/ROOT/build-minimal-teardown/lib/libRint.so
  #12 0x0000555555555303 in main ()

[vgvassilev]

@smuzaffar can you check this pr in cmssw?

[aaronj0]

force updated to trigger the CI which was down previously

[github-actions]

Test Results

    21 files      21 suites   3d 8h 55m 16s ⏱️
 3 831 tests  3 830 ✅ 0 💤 1 ❌
72 409 runs  72 407 ✅ 1 💤 1 ❌

For more details on these failures, see this check.

Results for commit e5bb010.

[smuzaffar]

@smuzaffar can you check this pr in cmssw?

@vgvassilev , cmssw tests passed. There are few unit test failures but they are not related to this change

[vgvassilev]

@smuzaffar can you check this pr in cmssw?

@vgvassilev , cmssw tests passed. There are few unit test failures but they are not related to this change

Thank you, @smuzaffar!