Bug 6604

Summary:	Severe Memory Leakage in X with AMD graphic cards
Product:	Mageia	Reporter:	Chih Wei Yao <elegant.pegasus>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	cjw
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	xsession-errors Xorg.0.log

Description Chih Wei Yao 2012-06-28 07:56:02 CEST

Description of problem:
I got a AMD 6670 with the machine running with Cauldron. After some update, the X eats up the memory as time goes. I had witnessed it ate up 3G of the memory.

Another phenomena is that after the memory usage goes beyond 400MB, then X would use up one of my CPU's core. The CPU would spend the whole core on X doing some I got no idea.

Version-Release number of selected component (if applicable):
x11-server 1.12.2


How reproducible:
Always

Steps to Reproduce:
1. Got a computer with AMD r600+
2. Boot it up with the Cauldron
3. Leave it there for some time, the memory usage would increase.

Comment 1 Chih Wei Yao 2012-06-28 07:56:45 CEST

Created attachment 2501 [details]
xsession-errors

Comment 2 Christiaan Welvaart 2012-06-28 22:41:15 CEST

The file   /var/log/Xorg.0.log   is more relevant for such a problem I think.
Do you have radeon-firmware from non-free installed?

CC: (none) => cjw

Comment 3 Chih Wei Yao 2012-06-29 10:05:54 CEST

Created attachment 2505 [details]
Xorg.0.log

Comment 4 Chih Wei Yao 2012-06-29 10:07:20 CEST

radeon-firmware is installed on my system

Comment 5 Chih Wei Yao 2012-07-05 15:38:24 CEST

Ping? Any other information needed?

This is really bugging me, when X used memory more than 350MB( I just discover the edge), the whole system becomes very slow.

Comment 6 Christiaan Welvaart 2012-07-11 02:34:01 CEST

You could try to use the open source "radeon" driver instead of fglrx.

Comment 7 Chih Wei Yao 2012-07-13 10:06:16 CEST

I got the same result for both driver. So I believe that's not limited to radeon or fglrx.

Comment 8 Chih Wei Yao 2012-08-13 07:28:57 CEST

Seems fixed in the update.

Status: NEW => RESOLVED
Resolution: (none) => FIXED