GPU Memory Leak about gslicr HOT 2 OPEN

Adding tmp_idx_img->Free() after line 87 in gSLICr_seg_engine_GPU.cu resolves the issue.

It's also worth noting that this only arises if you are allocating new input and output images to the GPU in successive calls. That is, these lines in my code:

// Instantiate a core_engine
gSLICr::engines::core_engine* gSLICr_engine = new gSLICr::engines::core_engine(_settings);

// gSLICr takes gSLICr::UChar4Image as input and output
gSLICr::UChar4Image* in_img = new gSLICr::UChar4Image(_settings.img_size, true, true);
gSLICr::UChar4Image* out_img = new gSLICr::UChar4Image(_settings.img_size, true, true);

For example, when I wrote a video SLIC-segmenting script (where the frames were all the same resolution), this was a non-issue as I only have to allocate once. However, if I recurse through a directory of images that may have different resolutions, I need to allocate whenever the image size has changed. In those circumstances, the memory leak appears.

from gslicr.

On a related note, there is a memory leak when the seg_engine is being repeatedly created and destroyed. I was wrong about the location, will update if/when I find out.

--Edit
I was gonna post a quick PR about tmp_idx_img, just so people are aware, only to find out there is one already.
#18

These need to be wrapped into smart pointers for more extensive usage.

from gslicr.