Fixes for 2 memory-leaks #19
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi 9ee1. Thanks for creating this project. I'm using it in a new project, which I will push to Github soon. While using your project I found 2 memory-leaks. I fixed them in my fork. Feel free to pull them to your branch.
The first memory-leak happens in CapstoneDisassembler.Disassemble() because the ownership of an disposable object is passed to this function. The object should then be disposed in this function.
The second memory-leak happens in CapstoneDisassembler.MoveNext(). It gets unmanaged data, which needs to be freed.