Memory leak on POSMAPOSL?

[AnderBiguri]

When I run POSMAPOSL, I can see that the RAM used slowly increases in each iteration, by a few megabytes, about 200 in my particular example (Discovery MI, 10 time-frames).

I discovered this by running the code in a machine with limited memory, and after several iterations, it would crash, as my expectation of used memory was only valid in the few first iterations.

[KrisThielemans]

Compile RelWithDebInfo and run via valgrind POSMAPOSL parfile. It will tell you about any leaks.

[AnderBiguri]

Will probably not do this anytime soon, recompiling the superbuild tends to add 3 days of work (because I make mistakes and there is some unexpected change), and I can simply allocate a bit more memory for my test (running at the CS cluster). Need to focus on other stuff now.

Simply reporting it here, for testing later, or for someone else to test.