memory initialisation in CHeapAllocator::Allocate about libczi HOT 2 CLOSED

Well, I'd think that it would be better to do the initialization only in places where it is necessary - so I'd put the clear-operation not into the "CHeapAllocator::Allocate". However - what you describe seems like a bug to me, but I am not sure what the operations are where you ran into this issue. Can you give some more details, or even better - a repro?

from libczi.

steps to reproduce:

• create a pixmap with a CreateSingleChannelScalingTileAccessor that is inside the bounding box
• lock, extract data, unlock
• create a second pixmap (same size) with the same accessor that is partly outside the bounding box
• lock, extract data, inlock

-> the extracted data that is outside the bounding box will still contain the pixel data from the first pixmap

from libczi.