Hi @alalek, I'm having OpenCV memory leak issues reported by heaptrack on Linux, I saw your pr is merging into version 3.4, I'm wondering if 4.x also has the same problem? Will you merge this into 4.x as well?

@alalek any plan to merge this into 4.x?

@CodArs-van , it have been merged to master.

Hi @alalek ．First of all, I am very grateful for the repair of the opencv async memory leak. This has also been verified after the update of the opencv version(such as 4.2), but now another problem encountered is somewhat similar. The same version(opencv 4.2) is also frequently used async (or std::thread)to open threads, in the child thread Calling opencv interfaces such as canny(or remap), there is a problem of continuous memory growth, do you know why?
This is my test code.

for (size_t i = 0; i < 1000000; i++) {
        std::async(std::launch::async, []() {
            cv::Mat binary_image_;
            std::cout << cv::utils::getThreadID() << std::endl;
            cv::Mat mImageGray = cv::imread("1.png", 1);
            cv::Canny(mImageGray, binary_image_, 12, 60);
        }).wait();
    }