"GStreamer" (GNOME Bugzilla)
2018-04-16 15:42:09 UTC
https://bugzilla.gnome.org/show_bug.cgi?id=795305
Bug ID: 795305
Summary: Gst.ValueList leaking memory
Classification: Platform
Product: GStreamer
Version: unspecified
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gst-python
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: ***@ubicast.eu
QA Contact: gstreamer-***@lists.freedesktop.org
GNOME version: ---
Created attachment 370993
--> https://bugzilla.gnome.org/attachment.cgi?id=370993&action=edit
reproduction script (python)
While working on a python script that reads spectrum messages, i noticed that
casting a Gst.ValueList does leak memory, as well as printing it.
Tapping directly into the array attribute does not trigger the leak.
I don't see what could cause this in the python gi override itself
(https://cgit.freedesktop.org/gstreamer/gst-python/tree/gi/overrides/Gst.py#n535)
I am unsure whether this could be lower level than the gst-python overrides,
please let me know if i should open a ticket somewhere else.
Bug ID: 795305
Summary: Gst.ValueList leaking memory
Classification: Platform
Product: GStreamer
Version: unspecified
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gst-python
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: ***@ubicast.eu
QA Contact: gstreamer-***@lists.freedesktop.org
GNOME version: ---
Created attachment 370993
--> https://bugzilla.gnome.org/attachment.cgi?id=370993&action=edit
reproduction script (python)
While working on a python script that reads spectrum messages, i noticed that
casting a Gst.ValueList does leak memory, as well as printing it.
Tapping directly into the array attribute does not trigger the leak.
I don't see what could cause this in the python gi override itself
(https://cgit.freedesktop.org/gstreamer/gst-python/tree/gi/overrides/Gst.py#n535)
I am unsure whether this could be lower level than the gst-python overrides,
please let me know if i should open a ticket somewhere else.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.