I hardly call making a reasoned guess "just guessing".

Sorry. But when the "reasoning" is nothing more than unfounded, unverified, 'pluck it out of thin air' speculation, there is no difference.

Care to explain what is going on? It certainly isn't what I thought.

No need. You just did.

• You guessed at what the problem might be. You made no attempt to verify your guess.
• You wrote a mountain of horribly complicated and convoluted code, with a frankly horrible interface.
• You used an architecture that could never address the stated problem, and that could never be implemented efficiently.

  Your current implementation uses 100% of one core when doing absolutely nothing at all.

• And then you threw it out there as a "solution", without having made even the most basic of tests that it met its stated goals.

And now you're going to make a big issue of the way I choose to bring these matters to your attention to divert from the real problem.

Oh! And BTW. There is no "intialization wipe-out bug". There is a clearly documented breach of new user expectations, that is easy to understand, and that has a documented solution. See shared_clone().

Albeit that, once you've written a few real applications, you'll find that it is rarely ever necessary to clone a non-shared data structure into a shared copy.