gnome-settings-daemon leaks memory / 100+ percent cpu

Bug #990695 reported by SlugiusRex
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Incomplete
High
Unassigned

Bug Description

gnome-settings-daemon leaks memory ( adds about 1 MB per minute )

Observed process use 100% + CPU utilization on one core for more than 30 minutes. Memory grew from about 200 MB to 390 MB during this 30 minute period.

Process status was reported as "Sleeping/futex_wait_queme_me". However, as soon as I typed 'ubuntu-bug' in the terminal it switched to Running ~ and then dropped its CPU usage to 60% and gave back 100MB of memory.

Then while typing this comment here.... it went back up to 102% and started consuming memory again.

See attached screenshot

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.2.2-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Apr 28 12:01:07 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
SlugiusRex (slugiusrex) wrote :
Revision history for this message
SlugiusRex (slugiusrex) wrote :

BTW the reason I post this is because I cant logout using gnome. (see CannotLogout Screenshot).

Also, I had VMware running ( but no VM was currently active )

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you get a gdb stacktrace? is the numlock status changing when that happens? seems similar to bug #969359

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
SlugiusRex (slugiusrex) wrote :

It is definitely the same as #483719 - which is classified as a duplicate of #969359.

So should I mark as duplicate?

I cannot reproduce. If it happens again I will obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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