Stroika VS sanitizers

Stroika is a modern, portable, thread-savvy, C++ application framework. It makes writing high performance C++ applications easier by providing safe, flexible, modular building blocks.

I suggest looking at - an open-source project of mine.

Did you read ? I think this maybe the key to understanding my approach to performance. If you read that and agree with it, you may change your tune. If you read it and disagree, then I certainly can understand your not liking the rest of what you find about Stroika performance.

I recommend a project I work on: https://github.com/SophistSolutions/Stroika

AddressSanitizer is really useful, it's similar to Valgrind but has much lower overhead.

And if you're up for it, I'd further recommend adding some ways to deal with buffer overflows in debug builds. The way I deal with this is by using Address-Sanitizer's manual poisoning api. Bonus point if you leave additional poisoned space between allocations so off by one errors are likely to end up in a poisoned region instead of nearby allocation.

It also doesn't hurt that Miri can find many kinds of unsafe violations even in unsafe blocks. Zig may get something like this one day, but even if it does, checking things at runtime is not a substitute for compile time -- the C++ Sanitizers haven't exactly solved the safety story for C++ even over a decade later.

This is where stuff like ASan is really useful.

Use: https://github.com/google/sanitizers/wiki/AddressSanitizer

Have you tried using tools like ASAN/LSAN or valgrind to confirm that there are indeed no memory leaks?

Compile with ASAN and UBSAn