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

Memory sanitizing #2870

Closed
clyne opened this issue Oct 4, 2021 · 2 comments
Closed

Memory sanitizing #2870

clyne opened this issue Oct 4, 2021 · 2 comments
Assignees
Milestone

Comments

@clyne
Copy link
Collaborator

clyne commented Oct 4, 2021

Valgrind reports a number of dynamic memory errors in the code base. We should try to eliminate as many as possible, starting with #2864, #2865, #2866, #2867, #2868.

N.B. some of the above issues report memory leaks in test drivers. The benefit of fixing leaks in test drivers is pretty minimal....

@clyne clyne added the High label Oct 4, 2021
@clyne clyne added this to the 3_6_0 Release milestone Oct 4, 2021
@shaomeng
Copy link
Collaborator

shaomeng commented Oct 4, 2021

A few numbers collected on 10/1/2021 to demonstrate this problem: I opened VAPOR, loaded a CF dataset, closed the dataset, and closed VAPOR. This process is monitored by Valgrind and it reports the following issues:

  • Conditional jump or move depends on uninitialised value(s) 40 occurrences.
  • Invalid read of size xyz 119 occurrences.
  • Use of uninitialised value of size xyz 30 occurences.
  • invalid file descriptor 6 occurences.
  • definitely lost memory blocks 222 occurrences.

@clyne
Copy link
Collaborator Author

clyne commented Dec 7, 2021

Addressed by separate sub issues (see above)

@clyne clyne closed this as completed Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants