<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Post-3.7.x memory leak, Radeon Evergreen, bisected" href="https://bugs.freedesktop.org/show_bug.cgi?id=60028#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Post-3.7.x memory leak, Radeon Evergreen, bisected" href="https://bugs.freedesktop.org/show_bug.cgi?id=60028">bug 60028</a> from <a class="email" href="mailto:dawitbro@sbcglobal.net" title="Dave Witbrodt <dawitbro@sbcglobal.net>"> Dave Witbrodt</a> <pre>(In reply to <a href="show_bug.cgi?id=60028#c7">comment #7</a>) > This is indeed more likely an issue in Mesa than in the kernel. The commit > you bisected also bumps KMS_DRIVER_MINOR in radeon_drv.c, which may cause > the Mesa code to use different code paths. In my two attempted manual reverts, I didn't know what effect the code in radeon_drv.c actually had. When looking at later DRM changes (after the one identified by the bisection) I saw that the value of KMS_DRIVER_MINOR was incremented further, so I thought I should leave the value unchanged. > Does current Mesa Git still leak? After updating/merging to the current HEAD (commit 02b6da1e of Jan. 29), I built new Mesa packages and installed them. I am currently relying the last kernel from my local tree which does not leak, so I rebooted to the kernel I had built that is most current with the upstream DRM changes: stable 3.7.4 + many commits from drm-next/drm-fixes up to commit 014b3440 of Jan. 21 in drm-fixes. Yes, it still leaks. Would it be good for me to bisect Mesa? I would use my most up-to-date kernel, try to find an older version of Mesa which does not leak, and then identify the first patch to Mesa which causes the leaking. The testing I have done so far was assuming the problem was in the kernel, but I was planning to look at Mesa as well. I decided to report the bug before continuing, hoping for some guidance from the experts. If there really is a memory leak caused by the kernel DRI, then I would like to help get it fixed before 3.8 is released; or, if there is a problem in Mesa I would like to help get it fixed for 9.1.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>