Comment=
# 6
on bug 90537<=
/a>
from Christian K=C3=B6nig
(In reply to pstglia from comment #5)=20
> Thanks for pointing this out. Just a question: I=
n 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 A=
10
> 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 wi=
th X
and other desktop environments for randeonsi is that when mesa drops the la=
st
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.
>=20
> However r600g/other drivers/hardwares can handle this in a different m=
anner
> 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.