@EricMEsch could you test if this PR fixes the memory leak you observed?

It does not seem to work. I tested and the memory consumption is still the same. I added a print statement inside of if(G4VVisManager::GetConcreteInstance() and it seems that if statement is true, even if i run in batch mode. If I run e.g. example 03-optics i will still see the print.

This is probably because in RMGManager::Initialize() the fG4VisManager is Initialized in any case. It might be a solution to just add a variable that will be set upon entering RMGManager::StartInteractiveSession()?

Edit: Nevermind, that variable already exists (fInteractive), there is just no getter for this variable yet

oh no, but fInteractive does not really help here. Visualization can also be used in batch files... (i.e. running a simulation and exporting an image file, like in our CI tests here). I will try some things to get the actual vis state from the manager...

please test again. the updated patch is now checking for the actual attached scene handler, and not just the manager.

Yes, now it works. Went from 24 GB memory consumption to 6 GB for my Simulations, that consists of a lot of optical photons each event.