comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Memory leak in IDL hdf5 library?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Memory leak in IDL hdf5 library? [message #74604 is a reply to message #74508] Mon, 24 January 2011 12:50 Go to previous messageGo to previous message
Eddie Schlafly is currently offline  Eddie Schlafly
Messages: 5
Registered: January 2011
Junior Member
Thanks for your help, David.

David Fanning writes:
> I don't notice any change on my Windows machines with or without this
> extra "close" statement, but I wonder if it would make a difference for
> you?

I take it that you don't see any leak under Windows?

Thanks for pointing out h5_close! I just followed the example files from
the hdf5 documentation, which didn't used h5_close.

If I add an h5_close at the end of ex_read_hdf5 and ex_create_hdf5, I no
longer leak memory. If, however, I just try to h5_close when I'm done
reading in a bunch of files, I still leak.

Adding h5_close, however, doesn't change the problem I am having where
the amount of memory used is many times the size of the file being read
in. The ~40K file I am reading in ends up reading in to about 50 MB of
memory, which is freed by the h5_close. The files are also slower to
read in than I would expect. If I write out a structure with a zero in
it, rather than a nested structure with a zero in it, things read in
quickly and no memory is leaked, even without h5_close.

Thanks a lot,

Eddie Schlafly
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: IDL 7 OK and IDL 8 segmentation Fault - JAVA BRIDGE
Next Topic: hai

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:54:24 PDT 2025

Total time taken to generate the page: 0.00393 seconds