Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDF4 test tst_h4_lendian fails valgrind #913

Closed
edhartnett opened this issue Mar 29, 2018 · 1 comment · Fixed by #922
Closed

HDF4 test tst_h4_lendian fails valgrind #913

edhartnett opened this issue Mar 29, 2018 · 1 comment · Fixed by #922

Comments

@edhartnett
Copy link
Contributor

The HDF4 test tst_h4_lendian fails valgrind like this:

==6719== 
==6719== HEAP SUMMARY:
==6719==     in use at exit: 544 bytes in 31 blocks
==6719==   total heap usage: 8,950 allocs, 8,919 frees, 10,631,683 bytes allocated
==6719== 
==6719== LEAK SUMMARY:
==6719==    definitely lost: 0 bytes in 0 blocks
==6719==    indirectly lost: 0 bytes in 0 blocks
==6719==      possibly lost: 0 bytes in 0 blocks
==6719==    still reachable: 544 bytes in 31 blocks
==6719==         suppressed: 0 bytes in 0 blocks
@edhartnett
Copy link
Contributor Author

OK, I have a fix for this working in HPC netCDF. When some PRs get merged I will put up a PR for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant