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

look for critical issues such as memory leak #30

Open
moghya opened this issue Nov 27, 2017 · 3 comments
Open

look for critical issues such as memory leak #30

moghya opened this issue Nov 27, 2017 · 3 comments

Comments

@moghya
Copy link
Owner

moghya commented Nov 27, 2017

make changes in library so as to reduce memory leaks.

@kauziishere
Copy link
Collaborator

Can we do an address-sanitizer/Valgrind run for this? to detect and remove any possible memory leaks?

@moghya
Copy link
Owner Author

moghya commented Aug 18, 2020

Definitely, that can be done, also there are some obvious bugs the code and need a round of review. I'll create and send out review requests.

@kauziishere
Copy link
Collaborator

that sounds better 👍🏼 you can just assign a few chunks of code to a few contributors.

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

2 participants