I'll have a look thanks.
Ethan
On Fri, Aug 16, 2013 at 9:23 AM, Ben Pfaff wrote:
> valgrind reports a couple of memory leaks for current master:
>
> ==25376== 84 bytes in 1 blocks are definitely lost in loss record 163 of
> 175
> ==25376==at 0x4D7B308: malloc (vg_replace_malloc.c:26
valgrind reports a couple of memory leaks for current master:
==25376== 84 bytes in 1 blocks are definitely lost in loss record 163 of 175
==25376==at 0x4D7B308: malloc (vg_replace_malloc.c:263)
==25376==by 0x80E2364: xmalloc (util.c:103)
==25376==by 0x8096244: mac_lear
I think that there are some memory leaks in the new meters code. I
don't, for example, see any "free" in ofproto_destroy() to match up
with this xzalloc() in ofproto_create():
ofproto->meters = xzalloc((ofproto->meter_features.max_meters + 1)
* sizeof(struct mete
