UMat/Mat lifetime warning

asked 2017-03-15 05:44:08 -0600

iko79
51 ●1 ●2 ●9

Hi, I'm currently trying to port my OpenCV 3.1 code to make use of OpenCL by replacing Mat objects with UMat and make adjustments accordingly. Now I saw the following warning:

! OPENCV warning: getUMat()/getMat() call chain possible problem.
!                 Base object is dead, while nested/derived object is still alive or processed.
!                 Please check lifetime of UMat/Mat objects!

What does this actually mean? I had a look into the source code of umatrix.cpp and saw that in the destructor the warning is shown when u->refcount is zero and u->urefcount is greater zero, but also when both are zero.

I'm not at all familiar with the in-depth implementation of OpenCV let alone the ocl part of it, so I have some trouble understanding what I'm doing wrong, so I would highly appreciate any related hints, thanks!

edit retag flag offensive close merge delete

Comments

can you show the piece of code causing the problem ?

berak ( 2017-03-15 06:07:19 -0600 )edit

I'll try to find it and extract it somehow, the codebase is pretty huge, so I am afraid this will be difficult. I was hoping that there are some general guidelines for using the ocl implementation of OpenCV, which could hint me to a possible problem... Is there something like a how-to/troubleshooting/common mistakes for porting to ocl?

iko79 ( 2017-03-15 06:51:46 -0600 )edit

add a comment

cv::UMat umat; cv::Mat mat(200, 400, CV_8U); umat = mat.getUMat(cv::ACCESS_RW, cv::UMatUsageFlags::USAGE_DEFAULT); // Not calling umat.release() would leave both until end of scope where the original // object (mat) could be destroyed first. umat.release();

UMat/Mat lifetime warning

Comments

1 answer

Links

Question Tools

Stats

Related questions

UMat/Mat lifetime warning edit

Comments

1 answer

Links

Question Tools

Stats

Related questions

UMat/Mat lifetime warning