| Priority | medium |
|---|---|
| Bug ID | 78366 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | [r600g] Memory leak desktop usage RV770 (HD4850) with 10.1.2 (related to not using LLVM anymore) |
| Severity | major |
| Classification | Unclassified |
| OS | Linux (All) |
| Reporter | vallesroc@gmail.com |
| Hardware | x86-64 (AMD64) |
| Status | NEW |
| Version | 10.1 |
| Component | Drivers/Gallium/r600 |
| Product | Mesa |
A long time ago (months? over a year?), I used to have this issue where mesa would cause the system to leak memory over time by just idling or browsing the web (kde, firefox) and at some point (just hours) it'd be bad enough (on 8GB RAM) that over 4GB swap would be used and system would be really slow because of that. Sorting processes by ram usage (on eg: top) would show no culprits; the memory was being leaked kernelside. Not even restarting X would fix the problem: A reboot was always necessary. The issue disappeared once I started building mesa with LLVM support... until now. 10.1.2 disables LLVM for RV770, which among other things fixes games such as DOTA2, but the problem is suddenly back, making me pretty sure it's linked to not using LLVM's shader compiler (or same thing, has to do with how shaders are compiled without LLVM).
(In reply to comment #1= ) > Sorting processes by ram usage (on eg: top) woul= d show no culprits; the > memory was being leaked kernelside. Not even restarting X would fix the > problem: A reboot was always necessary. That would be a kernel bug then. But it's hard to imagine how that could on= ly be triggered without LLVM... BTW, you can still enable LLVM via the environment variable R600_LLVM=3D1 or R600_DEBUG=3Dllvm.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | NOTOURBUG |
After trying with older mesa/llvm and experimenting around, I'= ve figured out it's not the same thing I used to have. Apparently, memory is recovered by closing Firefox. Top doesn't show it usi= ng that much memory, but it somehow does in less traceable ways. Damn firefox 29... I'm seriously considering moving to chromium now. Closing this bug.
(In reply to comment #2) > > Apparently, memory is recovered by closing Firefox. Top doesn't show it > using that much memory, but it somehow does in less traceable ways. Server side resources: http://www.freedesktop.org/wiki/Software/xrestop/