Georg Holzmann wrote:
Hallo!
This is a known memory leak in loading many files (image?) over time.
Did anyone narrow it down? I saw it first 2 years ago...
i tried today but couldn't find any problems (i did some benchmarking with loading 2 images several 1000 times alternatingly). leaktracer reported 288038 bytes being not freed (but this also happens when i was just loading the images a few times)
there is a possibility that the memory leak is in the caching done by [pix_image] (the cache could go infinitely large), which is not triggered when just loading 2 different images.
anyhow, could someone send a small patch that is known to leak ?
hm - that's interesting ... I also will use GEM in an installation in a few weeks ...
@Gem-devs: is this a bug in the image loader (image2mem), or specific to pix_image ? Or has anyone more infos?
i just noticed that there was a HUGE leak in [pix_buffer]'s "open"-message (not freeing the memory of the loaded image after the data was copied into the pix-buffer)
however, i have fixed that (in the CVS)
i haven't found any other leak (there is no caching done in pix_buffer, so i guess my assumptions are true even for 10000 different images)
mfg.a.dsr IOhannes