Bug 64943 - [HSW] gstreamer and mplayer memory leak
Summary: [HSW] gstreamer and mplayer memory leak
Status: VERIFIED FIXED
Alias: None
Product: libva
Classification: Unclassified
Component: intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: haihao
QA Contact: Sean V Kelley
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-24 08:01 UTC by Liu Tienan
Modified: 2013-08-12 01:58 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Gstreamer valgrind log on 5/20. (1.85 MB, text/plain)
2013-07-15 02:20 UTC, Yang Lianyue 		Details
Mplayer valgrind log. (19.04 KB, text/plain)
2013-07-15 06:28 UTC, Yang Lianyue 		Details
View All

Description Liu Tienan 2013-05-24 08:01:19 UTC 
Platform: HSW
Libva: staging branch 1fcd8cda3ed4e8491963533ef4c0f047de25e814
Intel-driver: staging branch add9ff7fee90144b0cd4b6d0d3240faffee49b69
Gst-plugins-ugly: 0.10 branch 9afc696e5fa9fb980e02df5637f022796763216f
Gst-plugins-bad: 0.10 branch 91f508fc14f5cb4aca63bab6609abd29a2dfe0ab
Gst-plugins-good: 0.10 branch 16dfcbe706d8d3dddfbc00c60145a1381a77fdc3
Gst-plugins-base: 0.10 branch 3359117536a062af9a0e946a603fd45e4c49560e
Gstreamer: 0.10branch c1fa5ba9fd993a1f4cd1a843773bdcb4889edbfe
Gst-vaapi: 0.4 branch e49e04a6aa9618b46d7a349a66372a16f3c690b3
mplayer: hwaccel-vaapi branch f1ad459a263f8537f6cba3bf479daea61c6104b9

Reproduce steps:
gstreamer_cmd: valgrind -v --tool=memcheck --leak-check=yes --log-file=valgrind.log gst-launch-0.10 filesrc location=mm.ts ! tsdemux ! vaapidecode ! vaapisink sync=false 
mplayer_cmd: valgrind -v --tool=memcheck --leak-check=yes --log-file=valgrind.log mplayer -vo vaapi 

And then check the file valgrind.log
Comment 1 haihao 2013-07-03 07:45:38 UTC 
Could you provide the log files ?
Comment 2 Yang Lianyue 2013-07-15 02:20:42 UTC 
Created attachment 82427 [details]
Gstreamer valgrind log on 5/20.
Comment 3 haihao 2013-07-15 05:58:59 UTC 
Was your libdrm built with valgrind enabled ? It seems valgrind doesn't recognize the pointer mapped by libdrm.
Comment 4 Yang Lianyue 2013-07-15 06:28:17 UTC 
Created attachment 82432 [details]
Mplayer valgrind log.
Comment 5 haihao 2013-08-07 02:53:48 UTC 
The lost in libva/driver has been fixed, but there are still some lost in other components. reassigne to gst guys.
Comment 6 Wind Yuan 2013-08-07 04:51:34 UTC 
If driver's fix(flowing leak) is done.
==1476==    at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==1476==    by 0xFF91563: __vaDriverInit_0_34 (i965_drv_video.c:4388)
==1476==    by 0xEEA6789: va_openDriver (va.c:293)
==1476==    by 0xEEA70B4: vaInitialize (va.c:476)
==1476==    by 0xF0D6594: gst_vaapi_display_constructed (gstvaapidisplay.c:532)
==1476==    by 0x5131B82: g_object_newv (gobject.c:1741)
==1476==    by 0x5131EC5: g_object_new_valist (gobject.c:1830)
==1476==    by 0x51321D3: g_object_new (gobject.c:1545)
==1476==    by 0xE13768E: gst_vaapi_ensure_display (gstvaapipluginutil.c:126)
==1476==    by 0xE13AAEB: gst_vaapisink_get_caps (gstvaapisink.c:396)
==1476==    by 0xD661F86: gst_base_sink_pad_getcaps (gstbasesink.c:606)
==1476==    by 0x4E877D5: gst_pad_get_caps_unlocked (gstpad.c:2254)

The gstramer log showed a leak in gst_update_registry. It's a dir path leak as bug https://bugs.freedesktop.org/show_bug.cgi?id=67285. it's a small gstreamer leak in init. this is out of our control. it's not necessary to fix.
I think we can close this bug.

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.