Ubuntu
compiz package

Pixmap memory leak in gtk-window-decorator

Bug #740258 reported by Tristan Tarrant on 2011-03-22

This bug affects 14 people

Affects		Status	Importance	Assigned to	Milestone
	Compiz Core	Fix Released	High	Sam Spilsbury	Compiz Core 0.9.7.0
	compiz (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: compiz

My Xorg process memory usage continues growing over time. Here it is after a few hours:

1498 root 20 0 426m 253m 20m S 12 6.4 12:10.87 Xorg

I have used xrestop to see where the memory is going. Here is the output:

xrestop - Display: :0.0
Monitoring 42 clients. XErrors: 2
Pixmaps: 215589K total, Other: 105K total, All: 215694K total

res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier
1800000 100 67 1 1087 207 183021K 9K 183031K 2546 gtk-window-decorator

Is there anything else I need to do ?

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-7.37-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.30 Fri Feb 25 14:34:55 PST 2011
GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-6ubuntu4)
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
CompositorRunning: compiz
Date: Tue Mar 22 16:08:39 2011
DistUpgraded: Log time: 2010-11-18 10:24:48.680131
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
vboxhost, 4.0.4, 2.6.38-7-generic, x86_64: installed
vboxhost, 4.0.4, 2.6.38-6-generic, x86_64: installed
vboxhost, 4.0.4, 2.6.35-28-generic, x86_64: installed
nvidia-current, 270.30, 2.6.38-7-generic, x86_64: installed
ExecutablePath: /usr/bin/gtk-window-decorator
GraphicsCard:
nVidia Corporation G96 [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:30f4]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=it_IT.utf8
LC_MESSAGES=en_GB.utf8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=8aea5427-9676-455f-8569-759b319e00f7 ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-7.37-generic 2.6.38
Renderer: Unknown
SourcePackage: compiz
UpgradeStatus: Upgraded to natty on 2010-11-18 (124 days ago)
XorgConf:
#Section "ServerFlags"
# Option "IgnoreABI" "1"
#EndSection
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.2C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30F4
dmi.board.vendor: Compal
dmi.board.version: 99.B6
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.2C:bd08/24/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.2C:rvnCompal:rn30F4:rvr99.B6:cvnCompal:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: F.2C
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.4-0ubuntu7
version.libdrm2: libdrm2 2.4.23-1ubuntu5
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

Tags:

Related branches

lp:~compiz/compiz/ubuntu

lp:ubuntu/precise/compiz

Revision history for this message

Tristan Tarrant (tristan-tarrant-gmail) wrote on 2011-03-22:

.proc.driver.nvidia.params.txt Edit (455 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (66.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (173.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (36.4 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (16.4 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (20.1 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (15.0 KiB, text/plain; charset="utf-8")
GlConf.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (18.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (891 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (38.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (803 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (126.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (287.0 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (975 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (27.1 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (32.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (13.0 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.1 KiB, text/plain; charset="utf-8")
drirc.txt Edit (303 bytes, text/plain; charset="utf-8")
monitors.xml.txt Edit (1.5 KiB, text/plain; charset="utf-8")
nvidia-settings.txt Edit (37.0 KiB, text/plain; charset="utf-8")
peripherals.txt Edit (1.1 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (22.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Omer Akram (om26er) wrote on 2011-03-31:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in compiz (Ubuntu):
status:	New → Incomplete

Revision history for this message

kr0n (amundsen) wrote on 2011-04-28:

valgrind-ati.log Edit (495.7 KiB, text/plain)

I have this problem to, just alt + tab with the application switcher plugin makes gtk-window-decorator consume more and more memory.

Im attachting the valgrind output of G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log compiz --replace

Let me know if i did it wrong.

This is with the xorg-server-video-ati drivers.

Revision history for this message

kr0n (amundsen) wrote on 2011-04-28:

valgrind-fglrx.log Edit (3.1 MiB, text/plain)

Here is a log using the fglrx drivers instead.

Revision history for this message

Sam Spilsbury (smspillaz) wrote on 2011-04-28: Re: [Compiz] [Bug 740258] Re: Pixmap memory leak in gtk-window-decorator

You'll need a valgrind log of the unity-window-decorator process.

On Thu, Apr 28, 2011 at 3:39 PM, kr0n <email address hidden> wrote:
> I have this problem to, just alt + tab with the application switcher
> plugin makes gtk-window-decorator consume more and more memory.
>
> Im attachting the valgrind output of G_SLICE=always-malloc G_DEBUG=gc-
> friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40
> --log-file=valgrind.log compiz --replace
>
> Let me know if i did it wrong.
>
> This is with the xorg-server-video-ati drivers.
>
> ** Attachment added: "valgrind-ati.log"
> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/740258/+attachment/2092503/+files/valgrind-ati.log
>
> --
> You received this bug notification because you are a member of compiz
> packagers, which is subscribed to compiz in Ubuntu.
> https://bugs.launchpad.net/bugs/740258
>
> Title:
> Pixmap memory leak in gtk-window-decorator
>
> _______________________________________________
> Mailing list: https://launchpad.net/~compiz
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~compiz
> More help : https://help.launchpad.net/ListHelp
>

--
Sam Spilsbury

Revision history for this message

kr0n (amundsen) wrote on 2011-04-28:

valgrind.log Edit (354.4 KiB, text/plain)

Right, I assume that means the gtk-window-decorator process.

Here is one.

Revision history for this message

Sam Spilsbury (smspillaz) wrote on 2011-04-28:

No, I meant unity-window-decorator :) the two are very different :)

On Thu, Apr 28, 2011 at 6:22 PM, kr0n <email address hidden> wrote:
> Right, I assume that means the gtk-window-decorator process.
>
> Here is one.
>
> ** Attachment added: "valgrind.log"
> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/740258/+attachment/2092657/+files/valgrind.log
>
> --
> You received this bug notification because you are a member of compiz
> packagers, which is subscribed to compiz in Ubuntu.
> https://bugs.launchpad.net/bugs/740258
>
> Title:
> Pixmap memory leak in gtk-window-decorator
>
> _______________________________________________
> Mailing list: https://launchpad.net/~compiz
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~compiz
> More help : https://help.launchpad.net/ListHelp
>

--
Sam Spilsbury

Revision history for this message

kr0n (amundsen) wrote on 2011-04-28:

valgrind.log Edit (372.6 KiB, text/plain)

As requested :)

Revision history for this message

Charlie Kravetz (cjkgeek) wrote on 2011-05-26:

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

I did not attempt to reproduce this issue. valgrind.log is attached for unity-window-decorator .

Changed in compiz (Ubuntu):
importance:	Undecided → Medium
status:	Incomplete → Triaged

Revision history for this message

Pavel Fischer (rubbiroid) wrote on 2011-07-10:

#10

Have the same bug. Simplest way to reproduce:
1. Set "Static Application Switcher" in Compiz as Application switcher
2. Open some Application
3. Open Task Manager
4. press Alt+Tab and look at Used Memory for gtk-window-decorator prozess

Revision history for this message

ThorX89 (thorx89) wrote on 2011-07-10:

#11

Is there a workaround or a fix?

Revision history for this message

Lukáš Chmela (lukaschmela) wrote on 2011-07-10:

#12

Yes, a workaround is to replace gtk-window-decorator with unity-window-decorator.

You can do it simply by pressing ALT+F2 and typing "gconf-editor", then navigating into "/apps/compiz-1/plugins/decor/screen0/options/" and changing the "command" key to "unity-window-decorator --replace".

Another way, however, non-persistent, is pressing ALT+F2 and typing directly "unity-window-decorator --replace &".
This way, the unity-window decorator would be replaced by the gtk one once Compiz is reloaded meaning that you would need to run this command on every login.

Hope this helps.

Revision history for this message

Lieven van der Heide (lievenvanderheide) wrote on 2011-08-14:

#13

I fixed this one in lp:~lievenvanderheide/compiz/PixmapLeakFix. The problem seemed to be that the author assumed GdkPixmap's was reference counted like a GtkObject (ie, initially a floating reference, which must be ref'ed to become a real reference). GdkPixmap doesn't derive from GtkObject though, and so uses GObject reference counting, which means it has an initial ref count of 1. I removed the two g_object_ref lines from switcher.c, which seems to fix the leaks.

Revision history for this message

Sam Spilsbury (smspillaz) wrote on 2011-08-15:

#14

Indeed that was the case, I found that too when I was working on
rewriting the decorator anyways.

Thanks for the patch, the fix will be applied in oneiric.

On Sun, Aug 14, 2011 at 11:08 PM, Lieven van der Heide
<email address hidden> wrote:
> I fixed this one in lp:~lievenvanderheide/compiz/PixmapLeakFix. The
> problem seemed to be that the author assumed GdkPixmap's was reference
> counted like a GtkObject (ie, initially a floating reference, which must
> be ref'ed to become a real reference). GdkPixmap doesn't derive from
> GtkObject though, and so uses GObject reference counting, which means it
> has an initial ref count of 1. I removed the two g_object_ref lines from
> switcher.c, which seems to fix the leaks.
>
> --
> You received this bug notification because you are a member of compiz
> packagers, which is subscribed to compiz in Ubuntu.
> https://bugs.launchpad.net/bugs/740258
>
> Title:
> Pixmap memory leak in gtk-window-decorator
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/740258/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~compiz
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~compiz
> More help : https://help.launchpad.net/ListHelp
>

--
Sam Spilsbury

Sam Spilsbury (smspillaz) on 2011-09-09

Changed in compiz-core:
status:	New → Fix Committed
importance:	Undecided → High
assignee:	nobody → Sam Spilsbury (smspillaz)
milestone:	none → 0.9.5.96

Revision history for this message

madbiologist (me-again) wrote on 2011-10-04:

#15

Is this fix included in the recently released compiz 1:0.9.6+bzr20110929-0ubuntu2 which is in the Oneiric repositories?

Area there any plans for an SRU for Natty?

Daniel van Vugt (vanvugt) on 2012-01-30

Changed in compiz-core:
milestone:	0.9.5.96 → 0.9.7.0

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-02-13:

#16

Download full text (6.6 KiB)

This bug was fixed in the package compiz - 1:0.9.7.0~bzr2995-0ubuntu1

---------------
compiz (1:0.9.7.0~bzr2995-0ubuntu1) precise; urgency=low

This bug was fixed in the package compiz - 1:0.9.7.0~bzr2995-0ubuntu1

---------------
compiz (1:0.9.7.0~bzr2995-0ubuntu1) precise; urgency=low

[ Didier Roche ]
  * New upstream snapshot:
    - Fix slow/stuttering display with fglrx (LP: #763005)
    - Don't dynamically link to compiz_core
    - Fix build failures with glib 2.30 (oneiric) (LP: #921406)
    - Fix uninitialized variable warnings in valgrind (LP: #921451)
    - Fixes up a bunch of boost::variant edge cases
    - Fixes a race condition where the xig restart test would fail spuriously
    - Incorrect (low/stuttering) refresh rate with NVIDIA driver (LP: #92599)
    - Benchmark window slows the system and degrades graphics resources
      (LP: #254561)
    - Windows that hide themselves when closed don't appear in any
      "this workspace" switcher  (LP: #684731)
    - hang in g_spawn_sync and select()  (LP: #690239)
    - word misspelled - bunding  (LP: #694169)
    - sometimes, restored window placed too high.  (LP: #716521)
    - Compiz clears the root window in the installer session  (LP: #720679)
    - unity-window-decorator: When switching between windows, Orca does
      not speak the title of the focused window.  (LP: #724093)
    - Cannot open a window that starts iconified  (LP: #732997)
    - Minimize animation flickr when for maximized apps  (LP: #737125)
    - Pixmap memory leak in gtk-window-decorator  (LP: #740258)
    - Windows should not automatically be focused when opened if the
      focus is on another application  (LP: #748840)
    - [sandybridge] Graphics tearing when playing video  (LP: #755841)
    - Compiz's "Sync to Vblank" makes display stutter/slow with fglrx
      (LP: #763005)
    - [regression] Moving windows lags behind the mouse by 1-2 seconds;
      appear to freeze when dragging.  (LP: #764330)
    - Launcher - Spread should not affect the state of window  (LP: #764673)
    - Clicking on a tweet/message link sometimes does not work  (LP: #790565)
    - scrolling on top of a close animation switches viewports  (LP: #795065)
    - unity video tearing when moving windows in oneiric with
      nvidia-current  (LP: #798868)
    - dialogs really slow to be displayed since the compiz update (LP: #812711)
    - It is possible to stack windows relative to windows that are
      destroyed  (LP: #837252
    - Should keep list of windows last sent to server and last recv
      from server  (LP: #841727)
    - compiz and X can disagree on the stacking order  (LP: #845719)
    - A minimized window 'remains' behind on the desktop if
      /apps/compiz-1/plugins/unityshell/screen0/options/
      show_minimized_windows is set to true  (LP: #847967)
    - maximized windows fail to update their input extents when
      undecorated  (LP: #853734)
    - resizing bugs with xterm  (LP: #854725)
    - crash on closing a window  (LP: #856015)
    - Java application windows cut-off/truncated/not displayed properly
      (LP: #857201)
    - compiz crashed with SIGSEGV in CompScreen::insertServerWindow()
      (LP: #857487)
    - compiz crashed with SIGABRT in raise()  (LP: #857738)
    - Applications which create multiple windows that are transients of
      each other can be given invalid stack positions  (LP: #858625)
    - Windows move to 0,0 on compiz restarts  (LP: #858629)
    - Crash when selecting Evolution in alt-tab  (LP: #859431)
    - invisible window when a window is mapped but not yet drawn on by
      the process mapping it  (LP: #860286)
    - race condition in configureXWindow causes unpredicatable window
      geometry changes  (LP: #860304)
    - windows that are decorated while resizing can cause incorrect
      resize results  (LP: #860306)
    - Moving a window while it is being resized by core caused
      unpredictable movement  (LP: #860309)
    - Windows which are marked transients of docks should be treated
      like docks  (LP: #860397)
    - can't maximize windows on second monitor and Qt windows displayed
      in wrong place  (LP: #861341)
  * debian/compiz-decorator, debian/compiz-gnome.install,
    debian/compiz-plugins-default.install,
    debian/compiz-plugins.install,
    debian/compiz-gnome.gconf-defaults, debian/rules, debian/unity.ini:
    - no more unity-window-decorator, switch back to gtk-window-decorator
    - remove plugins that are not shipped anymore
    - don't set in the default list plugins that are not shipped anymore
  * debian/libdecoration0.symbols:
    - upated to latest
  * Removed cherry-picked patches:
    - debian/patches/02_fix_autofocus_minimize_window.patch
    - debian/patches/03_fix_configureframe.patch
    - debian/patches/04_fix_insertServerWindow_crash.patch
    - debian/patches/05_fix_reconfigureXWindow_crash.patch
    - debian/patches/fix-748840.patch
    - debian/patches/fix-832150.patch
    - debian/patches/fix-863328.patch
    - debian/patches/fix-864330.patch
    - debian/patches/fix-864478.patch
    - debian/patches/fix-865863.patch
    - debian/patches/fix-866752.patch
    - debian/patches/fix-869316_869919.patch
    - debian/patches/fix-869967.patch
    - debian/patches/fix-886978.patch
    - debian/patches/fix_slow_vsync_lp763005.patch
    - debian/patches/rev_2821_fix_807487.patch
    - debian/patches/rev_2847_bug_796594.patch
    - debian/patches/rev_2878_bug_865696.patch
    - debian/patches/rev_2884_fix_874004.patch
    - debian/patches/rev_2890_fix_879253.patch
  * debian/rules:
    - the abi file is now renamed to core/abiversion.h
    - remove the .a
    - Remove -Bsymbolic-functions from LDFLAGS as it causes libcompiz_core to
      be loaded once per plugin when dlopened
    - don't run tests, they don't run on headless server anymore
  * debian/compiz-core.install:
    - contain new libcompiz-core lib
  * debian/compiz-kde.install:
    - do not ship kde part for now, it's broken upstream
  * debian/patches/ubuntu-config.patch:
    - default configuration is here now.
  * debian/patches/fix_gtk_w_d_crash.patch:
    - additional backport for gtk-w-d crash (LP: #930071)
  * debian/patches/fix_930412.patch:
    - backport to fix keybindings not working (LP: #930412)
  * debian/patches/fix_931283.patch:
    - trunk commit to fix a crash on shutdown (LP: #931283)
  * debian/patches/fix_924736.patch:
    - additional fix for getting the shadow active on maximized window
      (LP: #924736)

[ Sam Spilsbury ]
  * Remove unused plugins, disable tests by default
  * debian/patches/ccp_plugin.patch : force load the cpp plugin if not
    specified
  * debian/patches/workaround_broken_drivers.patch : workaround broken
    drivers that do binary detection
  * debian/patches/default_drag_key.patch : add a default in case mutter
    isn't installed
 -- Didier Roche <didrocks@ubuntu.com>   Mon, 13 Feb 2012 15:28:06 +0100

Changed in compiz (Ubuntu):
status:	Triaged → Fix Released

Daniel van Vugt (vanvugt) on 2012-03-03

Changed in compiz-core:
status:	Fix Committed → Fix Released

Revision history for this message

positivek (anonyhole) wrote on 2015-01-16:

#17

Still a problem in 14.04.1 LTS trusty.
Let me know what I can provide that would help localize the problem.

Revision history for this message

madbiologist (me-again) wrote on 2015-01-17:

#18

positivek - Can you please tell the details of your Xorg process in top, and your xrestop output. See this bug's description for examples. Also please attach a Valgrind log of your unity-window-decorator process - see https://wiki.ubuntu.com/Valgrind and https://wiki.ubuntu.com/X/DebuggingWithValgrind

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntucompiz package

Pixmap memory leak in gtk-window-decorator

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
compiz package