<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [r600g] Memory leak when playing WoW with RV790" href="https://bugs.freedesktop.org/show_bug.cgi?id=74539#c34">Comment # 34</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [r600g] Memory leak when playing WoW with RV790" href="https://bugs.freedesktop.org/show_bug.cgi?id=74539">bug 74539</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to <a href="show_bug.cgi?id=74539#c33">comment #33</a>) > This is the Xorg.0.log file from an instance where I didn't get > keyboard/mouse control back at all, and Xorg just chewed up 100% of one CPU > instead. DRICloseScreen is a DRI1 function; I suspect the backtraces in the Xorg log file aren't reliable. It would be interesting to see where the Xorg process is spinning, e.g. by attaching gdb to it and getting a couple of backtraces from it. (In reply to <a href="show_bug.cgi?id=74539#c32">comment #32</a>) > Perhaps not, but possibly worth asking Mr Greg KH if he'd be prepared to > consider it anyway? Sure, feel free to ask him. :) Anyway, any GPU resource leaks should be accompanied by 'normal' memory leaks, so valgrind should be the proper tool for the job.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>