← Back to team overview

compiz team mailing list archive

[Bug 1590136] [NEW] gtk-window-decorator using 6.3gb resident memory


Public bug reported:

I recently did a fresh install of ubuntu 16.04, then installed mate.
With only gnome terminal running, gtk-window-decorator is using 6.3
gigabytes of resident memory.

$ uptime
 16:10:01 up 1 day,  2:05,  4 users,  load average: 1.85, 2.17, 2.36
(with firefox open, the load seems high too - Xorg, compiz, mate-session, dbus-daemon....)

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                               
 2081 darxus    20   0 8392144 6.339g  18828 S   2.0 81.3  28:39.54 gtk-window-deco              

It's from compiz-gnome package Version:

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: compiz-gnome 1:
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: [core,composite,opengl,decor,wobbly,cube,td,rotate]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: MATE
Date: Tue Jun  7 16:07:36 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
 Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Barts XT [Radeon HD 6870] [1787:2010]
InstallationDate: Installed on 2016-05-28 (10 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
 [+73981.26s] DEBUG: Seat seat0 changes active session to 
 [+73984.20s] DEBUG: Seat seat0 changes active session to 25
 [+73994.32s] DEBUG: Seat seat0 changes active session to 
 [+73995.31s] DEBUG: Seat seat0 changes active session to c2
 [+73995.31s] DEBUG: Session c2 is already active
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=e18f152f-ce09-4257-a6ca-13ec4b6dd630 ro quiet splash
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3503
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A79T Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd05/06/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79TDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jun  6 14:04:29 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: radeon

** Affects: compiz (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.

  gtk-window-decorator using 6.3gb resident memory

To manage notifications about this bug go to:

Follow ups