Bug 704700

Summary: Leaked pixmaps are not freed when the X server exits
Product: [Fedora] Fedora Reporter: Matt McCutchen <matt>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: airlied, ajax, bskeggs, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:45:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Procedure and "free" output
none
/var/log/messages (messages from irrelevant user applications redacted)
none
dmesg output
none
Log from first X session
none
Log from second X session none

Description Matt McCutchen 2011-05-14 05:53:20 UTC
Description of problem:
gnome-settings-daemon appears to leak tens of megabytes worth of pixmaps per second while the monitor rotation menu is open (bug 704698).  With the nouveau driver, this memory shows as "used" in "top" output but does not belong to any process.  Disturbingly, the memory is not freed even if I go to single user mode.

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14.x86_64
kernel-2.6.35.13-91.fc14.x86_64

How reproducible:
Tried once.

Steps to Reproduce:
1. Leave the monitor rotation menu open for a little while as described in bug 704698 while watching the memory usage grow with "top".
2. Go to single user mode and check the memory usage again.

Actual results:
The leaked memory is still used.

Expected results:
The memory is freed.

Comment 1 Matěj Cepl 2011-05-14 18:17:27 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Matt McCutchen 2011-05-15 21:14:51 UTC
Created attachment 499052 [details]
Procedure and "free" output

A list of the steps I took and "free" output at various points.  The timestamps may help with interpreting the other logs.  About 500 MB more is used in the final measurement compared to the initial measurement, though both are in single user mode.

Comment 3 Matt McCutchen 2011-05-15 21:16:01 UTC
Created attachment 499053 [details]
/var/log/messages (messages from irrelevant user applications redacted)

Comment 4 Matt McCutchen 2011-05-15 21:16:33 UTC
Created attachment 499054 [details]
dmesg output

Comment 5 Matt McCutchen 2011-05-15 21:16:58 UTC
Created attachment 499055 [details]
Log from first X session

Comment 6 Matt McCutchen 2011-05-15 21:17:15 UTC
Created attachment 499056 [details]
Log from second X session

Comment 7 Fedora End Of Life 2012-08-16 12:45:41 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping