Hi,
Those two are still there with current master
(e0c4a59dc6c415c2abf6e0c5e3aaf5aee781cdf1).
False positive in Valgrind?
Cheers,
Tim
Am 24.01.2011, 16:53 Uhr, schrieb Joakim Sindholt :
Could you try updating to HEAD and trying again? Having just looked at
the cleanup code, it appears to be
Could you try updating to HEAD and trying again? Having just looked at
the cleanup code, it appears to be fixed.
On Mon, 2011-01-24 at 16:42 +0100, twied wrote:
> Hi,
>
> I think I found two memory leaks:
>
> Valgrind:
> ==27418== 112 bytes in 2 blocks are definitely lost in loss record 105 of 1
Hi,
I think I found two memory leaks:
Valgrind:
==27418== 112 bytes in 2 blocks are definitely lost in loss record 105 of 157
==27418==at 0x4C2380C: calloc (vg_replace_malloc.c:467)
==27418==by 0x8FCF794: r600_create_surface (r600_texture.c:419)
Code:
struct r600_surface *surface = CALL
