Open dmorissette opened 10 years ago
BTW, mapcache_seed is run with the following command:
mapcache_seed -c /path/to/mapcache/osm.xml -t osm-cache -e -12500000,9500000,-10000000,12000000 -n 8 -z0,15 -i "drill-down" -v
I was able to reproduce the leak on my system running Ubuntu 13.10. I used mapcache 1.2.1 and mapserver 6.2 with a pretty basic mapcache xml config (I used the default one and only changed the data source).
@tbonfort would you like to have a testcase?
Using mapcache_seed / MapCache 1.2.1 we have noticed what seems like a leak of projectionObj data, caused by the call to msLoadProjectionString() in _mapcache_source_mapserver_render_map() (source_mapserver.c)
We will try to produce a self-contained testcase, but in the meantime, here is what Valgrind reports for a short test and a longer run on the same maps:
Short test:
and the longer run reports larger amounts of memory leaked for the same lines of code:
I have verified with a simple loop that msLoadProjectionString() by itself doesn't leak in the same environment, so it seems to be something that mapcache_seed does that causes the leak. i.e. the following loop doesn't leak:
As I wrote we will try to produce a self-contained testcase unless you (@tbonfort) have an idea of what may be causing the leak?