Leite-sama / lavfilters

Automatically exported from code.google.com/p/lavfilters
GNU General Public License v2.0
0 stars 0 forks source link

Resource leak #473

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Using debug runtime of Direct3d9, I found that LAV video decoder leaks memory / 
resource using the attached video file (most materials should fail the same 
way).

To truly determine it is a fault of the decoder, I connected the LAV source 
splitter to LAV video decoder straight to null renderer.

This is the error:
Direct3D9: (ERROR) :Memory still allocated!  Alloc count = 37

Closing the graph and building it again causes alloc count to go up.

LAV video decoder specs:
v0.62
Hardware decoder Intel QuickSync
All other settings as per default

Switching Hardware decoder to "None" fixes the problem. So this is a QuickSync 
specific leak.

I can't test NVidia CUVID decoder as there is a separate bug that crashes the 
config dialog. A separate bug report to follow.

Original issue reported on code.google.com by zach....@gmail.com on 13 Aug 2014 at 7:15

Attachments:

GoogleCodeExporter commented 9 years ago
BTW, the mp4 file was obtained from 
https://archive.org/details/ligouHDR-HC1_sample1
On the same page, the Sample.mpg file also has the same problem.
So far I've only come across a single file that doesn't exhibit the leak issue 
-- BlackBerry.mp4 on this page 
http://download.wavetlan.com/SVV/Media/HTTP/http-mp4.htm

Original comment by zach....@gmail.com on 13 Aug 2014 at 7:18

GoogleCodeExporter commented 9 years ago
Direct3d9 debug settings:
Debug output level
Highest

Use debug version of D3d9
Max validation
Break on Mem Leaks
Break on D3D9 error

Original comment by zach....@gmail.com on 13 Aug 2014 at 7:24

GoogleCodeExporter commented 9 years ago
RE: I can't test NVidia CUVID decoder as there is a separate bug that crashes 
the config dialog

I have now tested CUVID and it works fine. There's no such leak. Hence this is 
a QuickSync specific bug.

Original comment by zach....@gmail.com on 13 Aug 2014 at 7:26

GoogleCodeExporter commented 9 years ago
You should report the problem to the author of the QuickSync decoder then, its 
an external component. You can find him here:

http://forum.doom9.org/showthread.php?t=162442

Original comment by h.lepp...@gmail.com on 15 Aug 2014 at 12:23