Changes between Initial Version and Version 2 of Ticket #3023


Ignore:
Timestamp:
Jun 9, 2009, 8:56:44 AM (15 years ago)
Author:
warmerdam
Comment:

I have tried running the command: 

gdalinfo -mm HDF4_EOS:EOS_SWATH:"MOD28L2.A2001213.1525.004.2002197060500.hdf":Swath:sst

under valgrind and there is no apparent memory leaks according to valgrind. Are you working on linux? Can you try using valgrind to identify the leaks you are encountering?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3023

    • Property Cc Kyle Shannon added
    • Property Keywords HDF4 added
    • Property Component default → GDAL_Raster
    • Property Status new → assigned

  • Ticket #3023 – Description

    initial v2  
    55
    66Using 64bit linux, gdal svn rev. 17228 (today), libhdf4.2r2, python 2.6.2
    7 
     7{{{
    88========= python code =========
    99
    … …  
    3838m2 = getmemory()
    3939print 'memory usage now:', m2, '  difference:', m2-m1
    40 
     40}}}