Please fill also the fields below. Note that root -b -q will tell you this info, and starting from 6.28/06 upwards, you can call .forum bug from the ROOT prompt to pre-populate a topic.
Sorry to read this. Hard to say though given the context shared so far. Do you have a minimal reproducer, standalone (create file, read it, segfault), we can work on?
Do you see the same issue with 6.32?
ROOT Version: 6.32.00
Built for macosxarm64 on Jun 21 2024, 22:29:45
From heads/v6-32-patches@tags/v6-32-00
and got the following
a.out(96246,0x1edc2cf40) malloc: nano zone abandoned due to inability to reserve vm space.
*** Break *** segmentation violation
[/usr/lib/system/libsystem_platform.dylib] _sigtramp (no debug info)
[/Users/user/Documents/testcpp/a.out] ROOT::Detail::TCollectionProxyInfo* ROOT::Detail::TCollectionProxyInfo::Generate<ROOT::Detail::TCollectionProxyInfo::Pushback<std::__1::vector<int, std::__1::allocator<int>>>>(ROOT::Detail::TCollectionProxyInfo::Pushback<std::__1::vector<int, std::__1::allocator<int>>> const&) (no debug info)
[/Users/user/Documents/testcpp/a.out] main (no debug info)
[/usr/lib/dyld] start (no debug info)
Thanks. We will have a look to this unit test.
However, can you share the an example that triggers this faulty behaviour during read/write of a collection?