Just FYI, this memory leak (just opening and closing a netcdf4 file)
is still there with hdf5-1.8.3-snap2 and netcdf-4.1-beta1-
snapshot2009061916. The leak appears for both generic netCDF-4 and
netCDF-4 classic model. It may not be an issue for most users, but I
run a python script that opens and closes a lot of netcdf files, and
it slows down substantially after about 1000 open/close cycles.
Best,
-- Ted
__________________________________________________________
| Edward Mansell <ted.mansell@xxxxxxxx>
| National Severe Storms Laboratory
| 120 David L. Boren Blvd.
| Room 4354
| Norman, OK 73072
| Phone: (405) 325-6177 http://www.cimms.ou.edu/~mansell
| FAX: (405) 325-2316
|
|
----------------------------------------------------------------------------
|
| "The contents of this message are mine personally and
| do not reflect any position of the U.S. Government or NOAA."
|
|
----------------------------------------------------------------------------
On Aug 28, 2008, at 11:42 AM, Jeff Whitaker wrote:
Ed Hartnett wrote:
Jeff Whitaker <jswhit@xxxxxxxxxxx> writes:
Hi all:
I found a memory leak, either in the netcdf-4 or HDF5 libs. To
reproduce it, run the simple_xy_wr.c example program to create a
file, then open and close it in a loop, monitoring the memory usage
with top. If the file is created in netcdf-3 (or netcdf-4 classic)
format, the memory usage remains constant. If the file is created
in
NETCDF4 format, the memory usage goes up and up. Here's the simple
program to trigger the leak. I've attached simple_xy_4.nc and
simple_xy_3.nc - the former will lead to a leak, the latter will
not.
Thanks!
I will look at this and let you know when it is fixed in the
snapshot...
Ed
Ed: Any progress on this one?
-Jeff
--
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/PSD R/PSD1 Email : Jeffrey.S.Whitaker@xxxxxxxx
325 Broadway Office : Skaggs Research Cntr 1D-113
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg
