Memory Leak in Intel VPL Hello-Encode-JPEG Sample

[Bhuvin]

Hi all,

I’ve been working with the hello-encode-jpeg sample from the Intel VPL GitHub repository (2.x API with internal memory management) and noticed a memory leak when modifying it to run in an infinite loop by resetting the input file pointer. I’d appreciate any insights on whether this is a bug in the sample, my modification, or expected behavior—and how to fix it properly.

To achieve continuous encoding , I added fseek(source, 0, SEEK_SET) after ReadRawFrame_InternalMem to reset the file pointer, keeping the while (isStillGoing) loop running. I'm observing a memory leak of ~100mb/min. 

Here is the original hello-encode-jpeg implementation.
https://github.com/intel/libvpl/blob/main/examples/api2x/hello-encode-jpeg/src/hello-encode-jpeg.cpp

And I have attached my modified version of the implementation.

Windows 11. Intel Iris Xe Graphics 31.0.101.4502

[mradul]

I have faced similar issue

[MountainDewd]

I am running into a similar problem

[kumak]

We wrote code based on the same sample and we have similar memory leak. Alot of time spent in using classical ways of matching allocation to deallocations but it is not clear why the memory leak remains. We first were blaming our code. But now it appears that the sample also shows a memory leak. Thanks @Bhuvin  for reporting. 
Has any one been able to solve it yet ?