Bug 64942

Summary: [HSW] libva memory leak
Product: libva Reporter: Liu Tienan <tienan.liu>
Component: intelAssignee: haihao <haihao.xiang>
Status: CLOSED NOTOURBUG QA Contact: Sean V Kelley <seanvk>
Severity: normal    
Priority: medium CC: lianyuex.yang, ouping.zhang
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Liu Tienan 2013-05-24 07:48:52 UTC 
Platform: HSW
Libva: staging branch 1fcd8cda3ed4e8491963533ef4c0f047de25e814
Intel-driver: staging branch add9ff7fee90144b0cd4b6d0d3240faffee49b69


Bug Info:
After the program, do not release the memory.

                                          Buffer     surface   picture    image
Base_Ext_Main_profile/FM1_FT_E.264        8          21        2          2
Mux_Stream/H264_352x240_frame45661.ts     0          21        2          2

Buffer 8 means the num of calling function vaCreateBuffer but not calling the function vaDestroyBuffer is 8 times.
surface  ——   vaCreateSurface
picture  ——   vaCreatePicture
image    ——   vaCreateImage

Reproduce steps:
Use LD_PRELOAD method to rewrite the source code, and print the calling infomation.
For example: 
1. LD_PRELOAD=va_memory_leak_checher.so mplayer -nosound -fps 30 -vo vaapi -va vaapi testcase 2>checker.2 >checker.1
2. the file checker.2 is the order of calling function.
Comment 1 haihao 2013-06-09 02:31:23 UTC 
It is the responsibility of user application not libva & libva driver to call vaDestroyXXX to release  VA resources.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.