<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#c6">Comment # 6</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>I do not know how to interpret these findings. I am not a developer, and work with the few tools that I (sort of) know how to use much more slowly than experienced developers would. I ran out of time over the weekend, and will have to investigate further this coming weekend. I have been trying to think of possible explanations: - could a later commit causes a similar (or identical) memory leak to the one caused by 4ac0533a? - is the problem really located somewhere else besides in the kernel DRM, such as in Mesa, with it being triggered by more than one kind of code change in the DRM? I thought that the bisection would be conclusive, but the failure of the revert attempts undermined my goal. If no one demands that I bisect using one of the drm-airlied branches, then I will try another custom branch which drops the commit first causing the leak, and see if any later commits also cause a leak. (If a developer demands that I bisect an upstream branch, I'll do that instead.) Is there anything else I can do to be helpful at this point? Can any of you confirm/reproduce this memory leak on your own systems?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>