Summary: | [HSW] gstreamer and mplayer memory leak | ||
---|---|---|---|
Product: | libva | Reporter: | Liu Tienan <tienan.liu> |
Component: | intel | Assignee: | haihao <haihao.xiang> |
Status: | VERIFIED FIXED | QA Contact: | Sean V Kelley <seanvk> |
Severity: | normal | ||
Priority: | medium | CC: | feng.yuan, lianyuex.yang, ouping.zhang |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Gstreamer valgrind log on 5/20.
Mplayer valgrind log. |
Description
Liu Tienan
2013-05-24 08:01:19 UTC
Could you provide the log files ? Created attachment 82427 [details]
Gstreamer valgrind log on 5/20.
Was your libdrm built with valgrind enabled ? It seems valgrind doesn't recognize the pointer mapped by libdrm. Created attachment 82432 [details]
Mplayer valgrind log.
The lost in libva/driver has been fixed, but there are still some lost in other components. reassigne to gst guys. 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.