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:
*** Bug 12010 has been marked as a duplicate of this bug. ***
CC: (none) => daniel_jackson
thanks
Keywords: (none) => UPSTREAMBlocks: (none) => 11844
More likely a bug in gstreamer
Assignee: bugsquad => olavSource RPM: totem-3.10.1-2.mga4.src.rpm => totem-3.10.1-2.mga4.src.rpm, gstreamer
CC: (none) => jani.valimaa, thierry.vignaud
(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'.
CC: (none) => goetz.waschk
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 => ASSIGNEDSource RPM: totem-3.10.1-2.mga4.src.rpm, gstreamer => gstreamer1.0-libav
are you working on it since you changed status ?
No, please assign to Funda, the gst-libav maintainer.
ok
Keywords: (none) => TriagedStatus: ASSIGNED => NEWAssignee: olav => fundawang
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
(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.
*** Bug 12386 has been marked as a duplicate of this bug. ***
CC: (none) => d.kalweit
Priority: Normal => release_blockerCC: (none) => stormiBlocks: (none) => 11704Summary: (upstream) Severe memory leak in Totem => (upstream) Severe memory leak in gstreamer
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
(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
on comment #13 so we can ask for push? or do we have to work on it more?
I'd say push it, the major bug is gone with this packages.
Packages have been submitted. Reporters please could you confirm this bug is fixed?
Keywords: (none) => NEEDINFOStatus: NEW => ASSIGNED
(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 :)
Great, thanks. according to comment #17 set to fixed
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED