Technically a Memory Leak

return 0; uint64_t ChookSystem::getAddressForTramp() { // yes, technically this creates a memory leak of 64B every hook creation. But I don't care. // tracking all the users of the memory would be painful // Nobody will look 100% times, and even if, that's only 64KB. Nothing. sAllocatedPack* page = nullptr; for (auto& page[...])

A programming code screenshot says that the code technically creates a 64-byte memory leak every time a hook is created, but the programmer does not care because nobody will inspect the memory and the leak is small. A grinning sunglasses emoji gives a smug reaction, making this useful as a joke about knowingly ignoring a minor technical problem. EN: A programming code screenshot says that the code technically creates a 64-byte memory leak every time a hook is created, but the programmer does not care because nobody will inspect the memory and the leak is small. A grinning sunglasses emoji gives a smug reaction, making this useful as a joke about knowingly ignoring a minor technical problem.

• @ithueti / 12389 2024-04-05