Coredump when appending a char to an std::string under high-load conditions
Recently I’ve seen a very weird core dump in someone’s code that only happens under very specific conditions: we only observer it when the corresponding part of our C++ service experiences an unusually high load.