On Fri, 16 Dec 2011 08:42:01 -0700
Brian Paul wrote:
> On 12/16/2011 07:17 AM, Pekka Paalanen wrote:
> > Valgrind complains about a definitely lost block allocated in
> > intelNewTextureImage(). This leak was apparently created by
> > 6e0f9001fe3fb191c2928bd09aa9e9d05ddf4ea9, "mesa: move
> > gl_t
On Fri, 16 Dec 2011 08:42:01 -0700
Brian Paul wrote:
> On 12/16/2011 07:17 AM, Pekka Paalanen wrote:
> > Valgrind complains about a definitely lost block allocated in
> > intelNewTextureImage(). This leak was apparently created by
> > 6e0f9001fe3fb191c2928bd09aa9e9d05ddf4ea9, "mesa: move
> > gl_t
On 12/16/2011 07:17 AM, Pekka Paalanen wrote:
Valgrind complains about a definitely lost block allocated in
intelNewTextureImage(). This leak was apparently created by
6e0f9001fe3fb191c2928bd09aa9e9d05ddf4ea9, "mesa: move
gl_texture_image::Data, RowStride, ImageOffsets to swrast", as it
removes t
Valgrind complains about a definitely lost block allocated in
intelNewTextureImage(). This leak was apparently created by
6e0f9001fe3fb191c2928bd09aa9e9d05ddf4ea9, "mesa: move
gl_texture_image::Data, RowStride, ImageOffsets to swrast", as it
removes the free() from _mesa_delete_texture_image().
Pu