Commen=
t # 15
on bug 74539<=
/a>
from Michel D=C3=A4nzer
(In reply to comment #=
14)
> Actually, I'm hoping that the valgrind output fr=
om WoW on my native 32 bit
> box will be sufficient.
If you could produce an apitrace reproducing the leaks as reported by valgr=
ind,
that might make it easier for us to reproduce and investigate the problem.
This one looks interesting, but I'm not sure yet how the memory ends up bei=
ng
leaked:
=3D=3D13334=3D=3D 302,736 bytes in 84 blocks are possibly lost in loss reco=
rd 6,231 of
6,282
=3D=3D13334=3D=3D at 0x400870E: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
=3D=3D13334=3D=3D by 0x8444B00: r600_texture_create_object (r600_texture=
.c:571)
=3D=3D13334=3D=3D by 0x844587C: r600_texture_create (r600_texture.c:759)
=3D=3D13334=3D=3D by 0x843FF69: r600_resource_create_common (r600_pipe_c=
ommon.c:589)
=3D=3D13334=3D=3D by 0x83DC5EF: r600_resource_create (r600_pipe.c:558)
=3D=3D13334=3D=3D by 0x81D7A98: st_texture_create (st_texture.c:96)
=3D=3D13334=3D=3D by 0x81AA32E: guess_and_alloc_texture (st_cb_texture.c=
:405)
=3D=3D13334=3D=3D by 0x81AA476: st_AllocTextureImageBuffer (st_cb_textur=
e.c:459)
=3D=3D13334=3D=3D by 0x814C953: _mesa_store_compressed_teximage (texstor=
e.c:4195)
=3D=3D13334=3D=3D by 0x81A99D4: st_CompressedTexImage (st_cb_texture.c:8=
23)
=3D=3D13334=3D=3D by 0x8138540: teximage (teximage.c:3244)
=3D=3D13334=3D=3D by 0x813A8D3: _mesa_CompressedTexImage2D (teximage.c:3=
913)