This pointer is called unconditionally in BarcodeImpl::initDecode
assuming the size of the image is outside the specified bounds. This
seems to not cause problems on optimized builds, I assume because the
optimizer sees through the processImageScale call to see that it can be
reduced to a resize call. Leaving it as is relies on undefined
behavior.
This was the least invasive change I could make, however, it might be
worthwhile to pull up the logic for a resize so that a SuperScale does
not need to be allocated, which seems to be the most common case.
