Bug 62311

Summary: [r600g] (kernel) memory leak
Product: DRI Reporter: Peter Barth <fdo>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: medium CC: fdo
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Peter Barth 2013-03-13 21:40:29 UTC
I'm experiencing a (kernel) memory leak for several months now and it seems to got worse. I found a bug on https://bugzilla.kernel.org/show_bug.cgi?id=43751#c11 but no solution yet (disregard command 12, it's not true ;)). I asked on IRC #fdo and #radeon and got told to file a bug here on fdo.

At some point I always run out of main memory and got lots of kernel messages like those:
[drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (4096, 6, 4096, -12)
[TTM] Out of kernel memory
[TTM] Out of kernel memory
Repeating over and over again. I'm currently running radeon driver 7.1.0, mesa 9.0.1, xorg-server 1.13.1, KDE 4.9.5 (tried with compositing enabled and disabled).

I don't know what to do or how to debug this, could anybody please help?
Comment 1 Jerome Glisse 2013-03-21 22:23:40 UTC
Try using non kde desktop for a while (gnome, xfce, ...) and see if you have same issue.
Comment 2 Peter Barth 2013-04-24 21:00:53 UTC
I'm running xfce for >3 weeks now without a problem. 

On a side note I'm still using most KDE apps I'm used to (konsole, konversation, akregator,...).
Comment 3 Marek Olšák 2014-01-23 14:10:25 UTC
It might be a memory link in KDE. Is this still an issue with the latest KDE and the latest Radeon driver components?
Comment 4 Peter Barth 2014-01-23 18:18:59 UTC
Currently running radeon driver 7.2.0, xorg-server 1.14.3 and kde 4.11.2 with no problem. So this bug can be closed.

However, I want to note that the memory wasn't freed even after shutting down kde,X,kdm,...

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.