[gdal-dev] PROJ 5.0.0

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[gdal-dev] PROJ 5.0.0

Kurt Schwehr-2
Anyone taken a look at PROJ since Sept?  I've tried a little bit to get it working for me, but I get memory leaks.

I was building staticly on debian testing and the leak sanitizer was very unhappy with 

Direct leak of 648 byte(s) in 1 object(s) allocated from:
    #0 0x55cc91c17533 in malloc third_party/llvm/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88:3
    #1 0x7fe2ea999ac1 in pj_malloc third_party/proj4/proj/src/pj_malloc.c:78:17
    #2 0x7fe2ea999b35 in pj_calloc third_party/proj4/proj/src/pj_malloc.c:93:17
    #3 0x7fe2ea9a4c3d in pj_utm third_party/proj4/proj/src/proj_etmerc.c:395:5
    #4 0x7fe2ea993bb3 in pj_init_ctx third_party/proj4/proj/src/pj_init.c:521:11
    #5 0x7fe2ea993382 in pj_init_plus_ctx third_party/proj4/proj/src/pj_init.c:412:14
    #6 0x7fe2ec7b7a26 in OCTProj4NormalizeInternal(char const*) third_party/gdal/ogr/ogrct.cpp:328:22
    #7 0x7fe2ec7b7824 in OCTProj4Normalize third_party/gdal/ogr/ogrct.cpp:357:16
    #8 0x7fe2ec793a5e in OGRSpatialReference::importFromProj4(char const*) third_party/gdal/ogr/ogr_srs_proj4.cpp:512:27

followed by a pile of indirect leaks with pretty much the same call stack

gdal-dev mailing list
[hidden email]