fix a memory leak

@thanks Mathieu Westphal for the report and patch

Change-Id: Ibd210e5456955d10f21443e853c299f07731b7c9
- FreeBSD, just like OSX, uses stat instead of stat64

Change-Id: Ief1911b72184635ea73581de1e5a66cf7d54b4c3
Add support for PNG compression in vtkPNGWriter

Change-Id: Ibae911d174ac101f22487459e30d8254a073a0b2
Merge branch 'master' of git://vtk.org/VTK into vtkPNGWriter-compression-support

Change-Id: Icd9f6490f4e74711eae4a1a85dcb014117c70027
Revise comment as per David's suggestion

Change-Id: I8c54b78f6b972cf0504ab2a30efd97275f7c6535
Merge topic 'FreeBSD-build-fixes' into master

d822e94f - FreeBSD, just like OSX, uses stat instead of stat64
Merge branch 'master' of git://vtk.org/VTK into vtkPNGWriter-compression-support

Change-Id: I810c7209a4279e06d08757d4f3b7e7082e3d314e
Revise comment as per Andrew's suggestion

Change-Id: Ieacca81cf86502b0f618b87ea90f2e730e1b6baa
Merge topic 'vtkPNGWriter-compression-support' into master

f660dc1b Revise comment as per Andrew's suggestion
61ae68a1 Merge branch 'master' of git://vtk.org/VTK into vtkPNGWriter-compression-support
d933d3c8 Revise comment as per David's suggestion
22136194 Merge branch 'master' of git://vtk.org/VTK into vtkPNGWriter-compression-support
5d97d7df Add support for PNG compression in vtkPNGWriter
MFixReader: Add support for 1.79 and up versions.

Change-Id: I2edee61a74beaa5cd2a4b5176a7f1eb623740a46
Remove vtkPTableToStructuredGrid and fix vtkTableToStructuredGrid for parallel

Change-Id: I677aa952b21475a6820f4ed8f2865107ad85c766
Update documentation/comment

Change-Id: I098f9106c942cac0bfe1db94aa71ba9350deb271
Merge topic 'table2structured_one_piece_extent_fix' into master

5c6f1766 Update documentation/comment
1094afc8 Remove vtkPTableToStructuredGrid and fix vtkTableToStructuredGrid for parallel
Merge topic 'mfix_updates' into master

0ec8ddbb MFixReader: Add support for 1.79 and up versions.
fix out of bounds pointer access when given 1D texture

This started showing up on Dash3 in TestControlPointsHandleItem
a few weeks back. I suspect driver change caused the resample path
to start being exercised there.

Change-Id: I98e9afea200c4b5ccfa44b2523f09590efb9ac35
Merge topic '0013322_plug_mem_leak' into master

9364db58 fix a memory leak
Merge topic 'fix_1D_texture_resampling' into master

e1982451 fix out of bounds pointer access when given 1D texture