Hi @clementhelsens,
a segmentation fault most likely indicates a bug in user code that leads to accesses to invalid memory regions (e.g. dereferencing a null pointer, out-of-bounds access of an array). Another possibility, if you are running with EnableImplicitMT, is that some of the operations that you schedule with RDF are not thread-safe (e.g. a Define that performs a TH1 fit is not thread-safe).
massif logs who allocates how much memory, we need a different kind of log to figure what’s going wrong. If you use a build of ROOT with debug symbols, it should print a stack-trace right after the crash, which shows where exactly things went wrong. If a stack-trace is not printed, we’ll need a small reproducer that we can run to debug this on our side.
Cheers,
Enrico