Hello,
It appears this bug has existed for quite a while. If someone could specify to me what the buffer size calculation logic is, I could probably get around it. The recommended function for specifying border behavior for the Dilate filter is ippiDilateBorder_<mod>, where I'm doing this on 16u. When calling: ippiMorphologyBorderGetSize_16u_C1R, pSpecSize comes back as -883236287 when specified with an ROI of 4068x5948 and a mask of 10017x10017, and a borderType of ippBorderRepl.
I noticed there are no morphological buffer size calculation functions, but with no specification for border behavior (ippiMorphGetSpecSize_L). First, will this function account for my border behavior? Second, this is only available in newer versions of IPP, which have a performance regression in the max filter for larger kernels and ROIs (as described in a post I resurrected from earlier today).
If someone can just tell me how this body of code calculates these buffer sizes, I can reproduce this with size_t types and get around this issue entirely.