Null is passed in to free() about lodepng HOT 3 OPEN

Well, unless this isn't intentional, I think this should be rather be considered a doocumentation issue and/or an issue with custom code. I mean, lodepng uses C-style allocation. So if somebody implements custom allocation, he/she must follow that (pretty much canonical) allocation scheme. But you didn't figure out or forgot this means deallocation handles NULL. So IMO the fix is to document that explicitly, not add extra code which is going to be duplicate anyway in 99% of cases out there.

from lodepng.

It's NULL not Null or null, and the both C anc C++ standards allow passing NULL to free in which case it does nothing, so I don't think this is an issue?

from lodepng.

Yes, whatever you call it, NULL or nullptr or 0 well anything that describes EAX = 00000000.

As i said its not an issue as it does not crash, however when I replaced it with my custom memory zone allocator I had unexpected a crashes because of it. So that is the reason i reported this. To fix this so that no one else like me runs into this, just put a null check with return in that function, should be good.

from lodepng.