Bug 1405574

Summary: possible memory leak in gamin
Product: Red Hat Enterprise Linux 6 Reporter: Joe Wright <jwright>
Component: gaminAssignee: Ondrej Holy <oholy>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.8CC: alanm, chhudson, rstrode, walters
Target Milestone: rcKeywords: Desktop, Regression
Target Release: 6.8   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-06 14:27:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joe Wright 2016-12-16 18:13:15 UTC
Description of problem:
- After patching for Dirty Cow, gam_server consumes excessive resources
- This is happening on RH6.x servers on which users are running vnc sessions using gnome desktop.  The gam_server process starts when the vncsession starts, and starts to consume CPU usage almost immediately.  An strace shows it is scanning automount filesystems.    The gam_server process will stop its CPU absorbtion once a user logs out of the vncsession and kills the vncserver process.  However, the gam_server process never exits.  It reduces its CPU usage slowly over time (it took 24 hours to go from 60% to 29%), but even when the user has logged out of the server, the gam_server process never exits.
- This is seen on almost all servers in use in a hardware farm.  It is expected they were just the first to notice it.  It is more likely to show up on all CEL6.x hosts where users are running vncsessions and using gnome desktop.

Version-Release number of selected component (if applicable):
- 2.6.32-642.6.2.el6.x86_64 with the Dirty COW patch
- gamin-0.1.10-9.el6.i686
- gamin-0.1.10-9.el6.x86_64
- gamin-python-0.1.10-9.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. unknown, other than update to kernel 2.6.32-642.6.2.el6.x86_64
2.
3.

Actual results:


Expected results:


Additional info:

It appears that the update to 2.6.32-642.6.2.el6.x86_64 with the Dirty COW patch seems to be the trigger here.

Comment 10 Red Hat Bugzilla 2023-09-14 03:36:23 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days