After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 790472 - Memory leak by using gst-play-1.0
Memory leak by using gst-play-1.0
Status: RESOLVED DUPLICATE of bug 788759
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.12.x
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-17 02:46 UTC by Fei
Modified: 2017-12-04 09:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test data (1.44 MB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2017-11-17 02:46 UTC, Fei
Details

Description Fei 2017-11-17 02:46:51 UTC
Created attachment 363876 [details]
test data

test cmd:
$ gst-play-1.0 --playlist=test.list --videosink="fakesink"

note: add Jurassic_World_2015_Trailer_2_5.1-1080p-HDTN.mp4 200 lines in test.list. Media stream link: http://videos.hd-trailers.net/Jurassic_World_2015_Trailer_2_5.1-1080p-HDTN.mp4

We used software&hardware decode for the testing and after running the cmd, RES from top keep increasing($ top -d -b | grep -i gst &> top.log). And attach graphics can show the RES change status.

software decode env:
gstreamer/gst-plugin-good/gst-plugin-ugly/gst-plugin-bad 1.12.3
gst-plugin-base 1.12.3 + commit ebb2fa6a0a2d2aa7d9f43cdac0087a9ceabb0240 


hardware decode by using gst-vaapi env:
Gstreamer: 7595c38a738abf830d3cccf5b31a38fc9ca6f6a6
Gst-plugin-base: 4c2f91d69e82917b3c1744bac87b8f120ec3f97f
Gst-plugin-good: 8aa5c59b5f78410b26d350731690ddfc1492809d
Gst-plugin-ugly: f86751d9f7a90ceea7a331edb5f54b314e7e3dd3
Gst-plugin-bad: f3b539e0ff88f8b7b49dee49929d5b3d94bda1a4
Gstreamer-vaapi: 14ed473dbde118aefd5cb55d134243f2a56e654b
Comment 1 rland 2017-11-17 03:01:04 UTC
This can provide any help?
https://bugzilla.gnome.org/show_bug.cgi?id=788759
Can you confirm it?
Comment 2 Sebastian Dröge (slomo) 2017-11-17 09:56:12 UTC
Does above patch fix it? Can you run with valgrind or some other software to get details about what exactly is leaked from where?
Comment 3 Fei 2017-11-20 02:52:55 UTC
Thanks Rolandz and Slomo, we will test this patch first.
Comment 4 Fei 2017-12-04 02:36:04 UTC
This patch fixed my issue, thanks.
Comment 5 Tim-Philipp Müller 2017-12-04 09:27:55 UTC

*** This bug has been marked as a duplicate of bug 788759 ***