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 610539 - screencast recording fills up my memory really fast
screencast recording fills up my memory really fast
Status: RESOLVED DUPLICATE of bug 632595
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2010-02-20 15:10 UTC by Jean-François Fortin Tam
Modified: 2012-01-10 07:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2010-02-20 15:10:07 UTC
GNOME Shell from the jhbuild script.

Intel Core2 Quad CPU (Q9300 @ 2.50GHz)
3.9 GiB of RAM
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)

Running at 1920x1200
Recording at 15 or 25 fps

My 4 GB of memory fill up within a minute of recording with the shell. This is pretty dangerous.
Comment 1 Dan Winship 2011-02-10 14:36:04 UTC
this was fixed by switching from theora to webm

*** This bug has been marked as a duplicate of bug 632595 ***
Comment 2 shrd 2012-01-10 07:52:57 UTC
I have the same problem with webm 
CPU Q6600 6 GB RAM
15 fps
desktop at 1680x1050
gnome-shell 3.2.1 (archlinux)  

 it take 3-4 mins (depending screencast) to go to the end of my 6GB of memory.
and worst : the memory is not released after. i I launch 4 different screencasts of 1 min, memory of gnome-shell goes to 6 gb.
 
i need to alt-f2 -> r to back to normal memory.
my system hangs if I go to the limit of my memory and i often need to reboot (i dont use swap with my 6b ram) . after my system goes to memory limit (6 GB) : dconf-service is running and use many IO and my system hangs , i can save it by ctrl alt f1 (very long) and login (take a while) and kill shellrecordersrc.

the problem occurs because the memory is not freed at the end of the shellrecordersrc process and during the process.

i have always seen this problem since i use gnome-shell