We are experiencing a leak when H265 is attempted decoded and the decoder is subsequently closed - it leaks memory.
Media SDK version: 2016.0.1
CPU: Any CPU pre Skylake that is supported by SDK
Steps to reproduce:
From individual threads, create several decoders and start decoding h.265 streams in 4K resolution.
Repeatedly close decoders and create new ones and continue decoding 4K h.265 streams.
You can keep decoding new streams without performance degradation.
After a while calls to SyncOperation() starts returning status code MFX_ERR_ABORTED. If you continue to destroy and create decoders, eventually the call to Init() on the SDK never returns, and you have effectively lost the thread the code is running in.
The CPU tested on: i7 4770K
Oh, forgot to mention :)
OS: Windows 10.
Also please note that the same code/application does not have this issue on 6-th gen CPU (Skylake). Seems to me that when the hybrid decoding is used on non-6th gen CPU there is a leak.
Sorry for the delay. I was able to reproduce the leak for HEVC SW decode plugin decode to video memory, but decode to system memory seems to work in my tests. A bug is filed for HEVC plugin SW decode to video memory. Do you see the leak for decode to system memory too?
Sorry this issue was taking so long and I didn't give you update.
I actually check the issue with dev team after my previous post at 2017 but they could not reproduce it. I actively worked on it for 2 weeks and then move to other projects.
I want to check with them again but do you have any updates on the latest release with the latest driver?
Dev team told me that they can not reproduce it with the following setup:
Yes this does not happen on Skylake++ CPUs, the issue was seen on Haswell and Broadwell.
In the mean time i will try to retest with new 2018 R2 SDK on Broadwell as well.
I also ask dev team to try on Broadwell, we also can't reproduce it.
Here are the test condition:
Processor: Intel(R) Core(TM) i5-5350U
OS: Windows 10
Driver: 18.104.22.16863 (latest product driver for 5th Gen from Intel.com)