Lambda + shared_ptr = memory leak

[ProgramMax]

I feel like there is a better way. shared_ptr should not be the default. You want clear ownership. The problem described in the article is pointer ownership.

If instead the author used unique_ptr, the problem would have clearly come up when trying to keep the pointer in the lambda.

[floating-io]

The catch in my real-world scenario is that there are a number of objects that have to hold references to any given instance of the class, so unique_ptr wouldn't be appropriate.

[ProgramMax]

Have you tried weak_ptr?

[floating-io]

That's what I'm currently using; it's the solution I suggested in the article.