<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - xserver-1.18.2 uses one core fully with dri3" href="https://bugs.freedesktop.org/show_bug.cgi?id=94596#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - xserver-1.18.2 uses one core fully with dri3" href="https://bugs.freedesktop.org/show_bug.cgi?id=94596">bug 94596</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Martin Peres from <a href="show_bug.cgi?id=94596#c19">comment #19</a>) > (In reply to Martin Peres from <a href="show_bug.cgi?id=94596#c18">comment #18</a>) > > I also bisected an issue to this commit, but this time not only was one core > > fully utilized, it was also leaking RAM at an impressive rate (600 MB/s). > > This would be when using the intel ddx. That happens under the same scenario as the busyspin - if we continually requeue multiple events to the same target vblank, we keep adding the new event to the currently queued vblank (by reallocating the event array). That will show up in the full-debug log quite nicely, I think.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>