Re: [AD] more about memory leaks |
[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]
> - ufile.c:170 has got a known leak, maybe not worth fixing > (but worth documenting) We can add a specific call to ff_match in al_findclose(): ff_match(NULL, NULL) for example would instruct the function to free its memory (patch attached, tested with Mandrake 8.0, commit it if you're ok). > - unicode.c:2611 leaks a single byte many times I can't reproduce it: which Allegro program do you use ? I mtraced the test program: tons of leaks, mostly in the interface between the config code and the unicode code, namely strdup(). But in allegro.c (btw, do you understand lines 383-384 ?), graphics.c, xwin.c, umodules and so on too. I'm going to concentrate upon the config/unicode part. -- Eric Botcazou ebotcazou@xxxxxxxxxx
Attachment:
ufile.diff
Description: Binary data
Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |