Processor: Intel Celeron 3955U @2.00 GHZ
Graphics Driver: Intel HD Graphics 510 (22.214.171.12463)
Operating System: Windows 7 - 64 bit
Intel Media SDK Version: 2016 - R2
Problem: A memory leak has been observed while using encoding (h264) frames with the the latest driver (126.96.36.19963) driver. The current beta driver also has the memory leak (188.8.131.5274)
I tried previously released drivers and can confirm that the 184.108.40.20600 driver does not have the memory leak. The memory leak seems be introduced in 220.127.116.1124 and still exist in newer drivers.
Steps to reproduce:
Encode a relatively input large file (> 30 GB) with the sample_encode.exe utility and observer memory usage in task manager:
sample_encode.exe h264 -i input.yuv -o output.264 -w 1920 -h 1080
Note: A large input file is used to prevent the sample_encode utility from ending quickly.
With 18.104.22.16863, the memory usage steadily increases. On the other hand, with 22.214.171.12400 memory usage is stable.
we can also confirm a memory leak on Skylake CPU (i5-6500) with driver version 126.96.36.19952. While we noticed the leak in our own software, we just tried the reproducer given by Ralph and can also observe a leak.
For our own software (encoding a live 1080p60 stream) the leak is around 20 kbyte/s. We observe the leak for H264 as well as for MPEG2 encoding (Ralph's reproducer can be used to confirm the issue for MPEG2 encoding).
As our system is expected to be running for several days, the leak unfortunately will reach a couple of GB...
Any updates on this would greatly be appreciated.
Hi Ralph & Peter,
Sorry for delayed response. I have tried on an i5 6300K, graphics adapter HDgraphics 530(same as Ralph's system should have), windows 8.1. Couldn't get my hands on the same configuration as yours but I couldn't replicate the issue. I am assuming this issue should be reproducible on this system as well.
cmd - \Intel Media SDK Samples 2016 188.8.131.52\_bin\x64>sample_encode.exe h264 -i C:\Users\Administrator\Documents\Videos\ducks_32k
frames.yuv -o out.264 -w 1920 -h 1080
Concatenated the ducks 1080p yuv for 32000 frames(size >90GB), memory consumption remain same throughout the session.
Ralph - Can you confirm if you see the issue on windows 7 or a different OS version?
Can please one of you provide snapshot of the issue like memory consumption at start of the session, middle of the session and towards the end?
I can see this issue on Windows 7 64-bit (Embedded Standard).
This is a memory snapshot (using Task Manager) during the test (184.108.40.20663)
Frame 1000: 59,600K,
Frame 10000: 60,900K
Frame 19000: 62,220K
Note: When I run the same test with an older driver (220.127.116.1100), memory usage is stable
Frame 1000: 63,640K
Frame 10000: 64,016K
Frame 19000: 63,972K
Let me know if you need anything else.
I was able to reproduce the issue and discussing this with the driver team. We are seeing better result with coming up driver on few systems but not on all. We are internally debugging this issue. Some of the folks are out of office next week which might can cause delays but I will keep you posted with progress.
Have a good weekend.
Also have the same issue.
I am using video surveillance software. Blueiris. And with these drivers, it consume 16GB of ram within 1 hour. Had to roll back to very old driver. I tried the beta drivers as well. But that still has the memory leak. Intel, please fix
Sorry for late response. I have tested the internal build today and issue is fixed in the latest driver which isn't public yet. Will update the public version of the driver details as soon as I have it.
Thank you for your patience.
I am also having this issue. My system configuration is
Intel NUC 6I5SYH
Intel Core i5-6260U CPU
Intel Iris Graphics 540
The leak is roughly 1 MB/s for encoding a 4K raw YUV video using hardware encoding with system memory
Anna B. (Intel) wrote:
What driver do you mean?
I can't reproduce memory leak with 18.104.22.16830 driver.
Hi Anna, the install filename I used is: win64_154028.4501
I can confirmed that same issue on i3-6100 HD530 with driver 22.214.171.12401 on Win10 x64 1511.
But, this issue not happened on i7-4790k HD4600 with driver 126.96.36.19901 on win10 x64 1511.
Until after update i3-6100 HD530 driver to 188.8.131.5231, the issue seem not happen again.