Revision history [back]

When the function reaches end of scope one particular UMat is failing to get deallocated and I'm getting this in call stack:

"UMat deallocation error: some derived Mat is still alive"

This is happening when I'm copying the UMat to Mat. If I dont copy to Mat then there is no issue. But I need the Mat version.

Code to reproduce:

cv::Mat x;
void some_function(cv::Mat x)
{
  cv::UMat y;
  x = y.getMat(cv::ACCESS_RW);
}

When the function reaches end of scope one particular UMat is failing to get deallocated and I'm getting this in call stack:

"UMat deallocation error: some derived Mat is still alive"

This is happening when I'm copying the UMat to Mat. If I dont copy to Mat then there is no issue. But I need the Mat version.

Code to reproduce:

cv::Mat x;
void some_function(cv::Mat x)
{
  cv::UMat y;
  x = y.getMat(cv::ACCESS_RW);
}