Opened 8 years ago

Closed 8 years ago

#45 closed defect (fixed)

Memory leak writing a NeXus file using compression

Reported by: Freddie Akeroyd Owned by: Mark Koennecke
Priority: major Milestone: NeXus 4.0 Release
Component: Version: 4.0rc1
Keywords: Cc: stephane.poirier@…

Description

It concerns a memory leak occuring only if one writes a NeXus file using compression.
I've made tests with zlib and szlib but the leak is present with both.
To show the problem the test program reads a binary file and writes its content as a dataset using (or not) the compression.

As attached files you'll find the test program, the binary data file and valgrind outputs with and without compression (LZW method with zlib)

All tests using Napi 4.0rc1 under linux rhel4 and compiled with gcc 3.4.4.

Best Regards,

Stephane.

Attachments (5)

valgrind_output_without_comp.txt (1.9 KB) - added by Freddie Akeroyd 8 years ago.
valgrind_output_with_comp.txt (1.9 KB) - added by Freddie Akeroyd 8 years ago.
comp_leak_test.cpp (2.1 KB) - added by Freddie Akeroyd 8 years ago.
binary.dat (512.0 KB) - added by Freddie Akeroyd 8 years ago.
leak_test3.log (551.3 KB) - added by Freddie Akeroyd 8 years ago.
More detailed valgrind output

Download all attachments as: .zip

Change History (8)

Changed 8 years ago by Freddie Akeroyd

Changed 8 years ago by Freddie Akeroyd

Changed 8 years ago by Freddie Akeroyd

Changed 8 years ago by Freddie Akeroyd

comment:1 Changed 8 years ago by Freddie Akeroyd

(In [904]) Add test provided by Stephane Poirier. Refs #45.

Changed 8 years ago by Freddie Akeroyd

More detailed valgrind output

comment:2 Changed 8 years ago by Freddie Akeroyd

(In [906]) Close property interface - think this fixes the leak. Refs #45.

comment:3 Changed 8 years ago by Freddie Akeroyd

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.