<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90537#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)" href="https://bugs.freedesktop.org/show_bug.cgi?id=90537">bug 90537</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to pstglia from <a href="show_bug.cgi?id=90537#c5">comment #5</a>) > Thanks for pointing this out. Just a question: In this case (bug on > application on mapping BOs/VAs) shouldn't we have a crash using other > drivers? With r600g we don't have this problem (tested with an ARUBA A10 > 5800K), just on radeonsi (at least on the tests I performed, which are > basically running "Antutu Benchmark" and some other apps). No crash, but just no more memory after a while. The reason why it works with X and other desktop environments for randeonsi is that when mesa drops the last reference the VA range is freed automatically as well. But in your case it looks like that mesa drops the last reference and the buffer isn't freed. This means that somebody has still a reference to the buffer which is a bit odd. It probably points to a bug somewhere. > > However r600g/other drivers/hardwares can handle this in a different manner > of course, which could explain why we don't experience this on other > hardwares. R600 hardware uses command stream patching instead of virtual memory, so you never run into this issue. Regards, Christian.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>