Bug 12142 - (upstream) Severe memory leak in gstreamer
Summary: (upstream) Severe memory leak in gstreamer
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: release_blocker critical
Target Milestone: ---
Assignee: Funda Wang
QA Contact:
URL: https://bugzilla.gnome.org/show_bug.c...
Whiteboard:
Keywords: NEEDINFO, Triaged, UPSTREAM
: 12010 12386 (view as bug list)
Depends on:
Blocks: 11704 11844
  Show dependency treegraph
 
Reported: 2013-12-28 22:55 CET by Reinout van Schouwen
Modified: 2014-01-25 21:30 CET (History)
8 users (show)

See Also:
Source RPM: gstreamer1.0-libav
CVE:
Status comment:


Attachments

Description Reinout van Schouwen 2013-12-28 22:55:21 CET
Description of problem:
Already found in Gentoo and reported in upstream Gnome bugzilla (bgo 721077), but filing in Mageia bugzilla as a reminder for MGA4. 

Version-Release number of selected component (if applicable):
3.10.1

How reproducible:
Always

Steps to Reproduce:
1. Play an mp4 file with Totem
2. Watch memory usage skyrocket and system grind to a halt
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-12-29 11:35:08 CET
*** Bug 12010 has been marked as a duplicate of this bug. ***

CC: (none) => daniel_jackson

Comment 2 Manuel Hiebel 2013-12-29 11:36:07 CET
thanks

Keywords: (none) => UPSTREAM
Blocks: (none) => 11844

Comment 3 Thierry Vignaud 2013-12-29 11:44:25 CET
More likely a bug in gstreamer

Assignee: bugsquad => olav
Source RPM: totem-3.10.1-2.mga4.src.rpm => totem-3.10.1-2.mga4.src.rpm, gstreamer

Thierry Vignaud 2013-12-29 11:47:50 CET

CC: (none) => jani.valimaa, thierry.vignaud

Comment 4 Reinout van Schouwen 2013-12-29 15:15:24 CET
(In reply to Thierry Vignaud from comment #3)
> More likely a bug in gstreamer

FWIW, the upstream bug reporter says 'The same files play all right using gst-launch-1.0'.
Götz Waschk 2013-12-30 17:19:13 CET

CC: (none) => goetz.waschk

Comment 5 Götz Waschk 2014-01-10 17:54:06 CET
I happened because we build our gst-libav against ffmpeg instead of using the bundled libav. Upstream git of gst-libav has a fix that applies cleanly against gst-libav 1.2.2.

Status: NEW => ASSIGNED
Source RPM: totem-3.10.1-2.mga4.src.rpm, gstreamer => gstreamer1.0-libav

Comment 6 Manuel Hiebel 2014-01-10 20:00:24 CET
are you working on it since you changed status ?
Comment 7 Götz Waschk 2014-01-10 20:10:37 CET
No, please assign to Funda, the gst-libav maintainer.
Comment 8 Manuel Hiebel 2014-01-10 20:22:53 CET
ok

Keywords: (none) => Triaged
Status: ASSIGNED => NEW
Assignee: olav => fundawang

Comment 9 Anne Nicolas 2014-01-19 23:35:00 CET
Funda, can you please have a look on that one. We need to have it fixed for final release in 2 weeks. Thanks in advance

CC: (none) => ennael1

Comment 10 Götz Waschk 2014-01-21 09:06:56 CET
(In reply to Anne Nicolas from comment #9)
If you don't want Funda to fix this, you could upgrade of gstreamer to version 1.2.2 and apply that patch to gst-libav 1.2.2.
Comment 11 Manuel Hiebel 2014-01-21 19:30:06 CET
*** Bug 12386 has been marked as a duplicate of this bug. ***

CC: (none) => d.kalweit

Samuel Verschelde 2014-01-23 12:57:46 CET

Priority: Normal => release_blocker
CC: (none) => stormi
Blocks: (none) => 11704
Summary: (upstream) Severe memory leak in Totem => (upstream) Severe memory leak in gstreamer

Comment 12 Angelo Naselli 2014-01-23 22:47:44 CET
In reply to comment #10  Götz Waschk, during this night meeting we
agreed to upgrade to 1.2.2, someone said you already started to work on it, is it true? can you please commit your changes?

If you cannot work on it i will try this week-end, but i seem i cannot replicate
the problem here :/

Another question is the patch you are referring to this one:
http://cgit.freedesktop.org/gstreamer/gst-libav/commit/?id=ca1b5d85765be8df27d0a87a45426c7925ce1f29 ?

TIA,
  Angelo

CC: (none) => anaselli

Comment 13 Götz Waschk 2014-01-23 22:59:55 CET
(In reply to Angelo Naselli from comment #12)
> In reply to comment #10  Götz Waschk, during this night meeting we
> agreed to upgrade to 1.2.2, someone said you already started to work on it,
> is it true? can you please commit your changes?
OK done. I have committed these:
gstreamer1.0
gstreamer1.0-plugins-bad
gstreamer1.0-plugins-good
gstreamer1.0-libav
gstreamer1.0-plugins-base
gstreamer1.0-plugins-ugly

> If you cannot work on it i will try this week-end, but i seem i cannot
> replicate
> the problem here :/
It depends on the video-sink in use, check the upstream bug please.

> Another question is the patch you are referring to this one:
> http://cgit.freedesktop.org/gstreamer/gst-libav/commit/
> ?id=ca1b5d85765be8df27d0a87a45426c7925ce1f29 ?
That must be a followup, I was referring to 81cef109e20cbce285bacaf673597aef57fc30f3
Comment 14 Angelo Naselli 2014-01-23 23:43:33 CET
on comment #13 so we can ask for push? or do we have to work on it more?
Comment 15 Götz Waschk 2014-01-24 09:57:43 CET
I'd say push it, the major bug is gone with this packages.
Comment 16 Angelo Naselli 2014-01-24 21:30:26 CET
Packages have been submitted. Reporters please could you confirm this bug is fixed?

Keywords: (none) => NEEDINFO
Status: NEW => ASSIGNED

Comment 17 Daniel Kalweit 2014-01-25 20:08:22 CET
(In reply to Angelo Naselli from comment #16)
> Packages have been submitted. Reporters please could you confirm this bug is
> fixed?

Sorry, that I'm a little bit late...

Now it works fine for me again!

A big THANK YOU for everyone who worked on it :)
Comment 18 Angelo Naselli 2014-01-25 21:30:31 CET
Great, thanks.

according to comment #17 set to fixed

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.