Segfault when running Moore test multi-threaded with output

Trying to run the hlt2_thor_selections test multi-threaded with MDF output results in a segfault. Running on a dbg+asan build shows

==26721==ERROR: AddressSanitizer: attempting double-free on 0x602000a34850 in thread T20:
    #0 0x7fd340d54237 in operator delete(void*, unsigned long) /build/gcc/WORK/build/contrib/gcc-10.1.0/src/gcc/10.1.0/libsanitizer/asan/asan_new_delete.cpp:172
    #1 0x7fd3123ce23c in __gnu_cxx::new_allocator<LHCb::ParticleID>::deallocate(LHCb::ParticleID*, unsigned long) /cvmfs/lhcb.cern.ch/lib/lcg/releases/gcc/10.1.0/x86_64-centos7/include/c++/10.1.0/ext/new_allocator.h:133
    #2 0x7fd3123cc459 in std::allocator_traits<std::allocator<LHCb::ParticleID> >::deallocate(std::allocator<LHCb::ParticleID>&, LHCb::ParticleID*, unsigned long) /cvmfs/lhcb.cern.ch/lib/lcg/releases/gcc/10.1.0/x86_64-centos7/include/c++/10.1.0/bits/alloc_traits.h:492
    #3 0x7fd3123c8ccf in std::_Vector_base<LHCb::ParticleID, std::allocator<LHCb::ParticleID> >::_M_deallocate(LHCb::ParticleID*, unsigned long) /cvmfs/lhcb.cern.ch/lib/lcg/releases/gcc/10.1.0/x86_64-centos7/include/c++/10.1.0/bits/stl_vector.h:354
    #4 0x7fd311da6123 in void std::vector<LHCb::ParticleID, std::allocator<LHCb::ParticleID> >::_M_realloc_insert<LHCb::ParticleID const&>(__gnu_cxx::__normal_iterator<LHCb::ParticleID*, std::vector<LHCb::ParticleID, std::allocator<LHCb::ParticleID> > >, LHCb::ParticleID const&) /cvmfs/lhcb.cern.ch/lib/lcg/releases/gcc/10.1.0/x86_64-centos7/include/c++/10.1.0/bits/vector.tcc:500
    #5 0x7fd311da42b4 in std::vector<LHCb::ParticleID, std::allocator<LHCb::ParticleID> >::insert(__gnu_cxx::__normal_iterator<LHCb::ParticleID const*, std::vector<LHCb::ParticleID, std::allocator<LHCb::ParticleID> > >, LHCb::ParticleID const&) (/home/lmeyerga/stack-280721-dbg/LHCb/InstallArea/x86_64_v2-centos7-gcc10-dbg+asan/lib/libPartPropLib.so+0xa12b4)
    #6 0x7fd311d9f714 in Decays::Nodes::CTau::addToAccepted(LHCb::ParticleID const&) const ../Kernel/PartProp/src/NodePIDs.cpp:472

It seems to be caused by local caches being manipulated in NodesPIDs.cpp. Call stack

FYI @sstahl @rmatev