I'm running a fairly simple transcode which is showing a memory leak when encoding JPEGs with driver version 220.127.116.1139 on Windows 10 with a i7-6770HQ CPU / Iris Pro 580 GPU.
I have run two separate processing pipelines. First is an mpeg2 decode to an h264 encode; this runs just fine with no noticeable leaks. Changing just the initialisation code for the encoder to perform a JPEG encode instead of h264, I see a significant leak of the order of ~450MB over the course of around 12 minutes. This is doing 25 frames per second, so assuming the leak is per-frame then it is around 25KB per frame.
Again, literally the only difference between the two runs was changing the parameters to the the MFXVideoENCODE_Init call, so I am pretty confident that this is a leak in the driver rather than in my surrounding code.
One additional point, the encoder is reporting MFX_WRN_PARTIAL_ACCELERATION when initialising; I was expecting JPEG encodes on Skylake to be hardware. Don't know if that's related to the leak or a subject for another post.
Any ideas on how to diagnose the leak further?
Another update - I just found this thread https://software.intel.com/en-us/node/699527, and can confirm that driver version 18.104.22.16834 appears to have solved the memory leak. Is there likely to be an update to the latest version soon which includes this fix? Just slightly surprised that an older driver version apparently contains a newer media version than a later driver - make it kind of hard to know which driver should be getting installed!