On 15 February 2013 23:16, Eric Anholt wrote:
> christopher.halse.rog...@canonical.com writes:
>
> > From: Christopher James Halse Rogers
> >
> > _mesa_delete_renderbuffer does not call the driver-specific
> > renderbuffer delete function, so the blorp code was leaking the
> > Intel-specific bit
christopher.halse.rog...@canonical.com writes:
> From: Christopher James Halse Rogers
>
> _mesa_delete_renderbuffer does not call the driver-specific
> renderbuffer delete function, so the blorp code was leaking the
> Intel-specific bits, including some GEM objects.
>
> Call the renderbuffer's ->
From: Christopher James Halse Rogers
_mesa_delete_renderbuffer does not call the driver-specific
renderbuffer delete function, so the blorp code was leaking the
Intel-specific bits, including some GEM objects.
Call the renderbuffer's ->Delete() method instead, which does the
right thing.
Fixes