Comment=
# 7
on bug 90537<=
/a>
from Michel D=C3=A4nzer
(In reply to Christian K=C3=B6nig from comment #6)
>=20
> 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.
>=20
> It probably points to a bug somewhere.
Not necessarily if the BO is shared. E.g. in the Xorg radeon driver we have=
to
leak a reference to the fbcon BO because of this issue.
Another possibility is that the same BO is referenced by several GEM handle=
s in
the same DRM fd, e.g. because it's re-imported via GEM flink. In that case,=
my
patch is probably the wrong solution, as it would make the BO unusable via =
the
other GEM handle.