Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#18366 - [libdrm] 2.4.17-4 memory-leak
Attached to Project:
Arch Linux
Opened by Martin Baselier (martinbaselier) - Wednesday, 17 February 2010, 00:27 GMT
Last edited by Dan Griffiths (Ghost1227) - Friday, 26 February 2010, 02:43 GMT
Opened by Martin Baselier (martinbaselier) - Wednesday, 17 February 2010, 00:27 GMT
Last edited by Dan Griffiths (Ghost1227) - Friday, 26 February 2010, 02:43 GMT
|
DetailsDescription:
After upgrading to 2.4.17.4 a memory leak occurs. When opening and closing applications, X grows in size (specifically the virtual memory as shown in top) Downgrading to 2.4.17.3 solved it for me. Additional info: hardware: R300 compatible video card (VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE)) integrated in an acer TM8100 * package version(s) mesa: 7.7-1 libgl: 7..7-1 xf86-video-ati: 6.12.4-3 * kernel : linux-api-headers 2.6.32.5-2 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 9 14:46:08 UTC 2010 i686 Steps to reproduce: open a terminal and use top for monitoring: top -p `ps -C X -o pid | grep -v PID` open and close random programs and watch the size of X (in my case aisleriot, lmms just FYI: Memory leaks in X have haunted me in newer version of X on my hardware for some time now. (in several distributions) Since it was recently solved in arch I constantly monitor the memory size of X. |
This task depends upon
Closed by Dan Griffiths (Ghost1227)
Friday, 26 February 2010, 02:43 GMT
Reason for closing: Works for me
Additional comments about closing: Appears to work fine in most recent release.
Friday, 26 February 2010, 02:43 GMT
Reason for closing: Works for me
Additional comments about closing: Appears to work fine in most recent release.
Comment by Jan de Groot (JGC) -
Thursday, 18 February 2010, 14:24 GMT
2.4.17-3 and 2.4.17-4 only have a few intel-related changes applied. For ATI/AMD there's no difference between both packages.
Comment by Martin Baselier (martinbaselier) -
Thursday, 25 February 2010, 20:11 GMT
upgraded to libdrm 2.4.18-2 and no problem there. Strange that it occurred when there should not have been differences between both packages. I'll keep an eye on it anyway, because I've been having similar problems in the past and they keep reoccurring.