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 Leak #21

Open
MrIsland opened this issue Nov 24, 2021 · 2 comments
Open

Memory Leak #21

MrIsland opened this issue Nov 24, 2021 · 2 comments

Comments

@MrIsland
Copy link

MrIsland commented Nov 24, 2021

Hi !
Really a fantastic project! It really makes great progress for my project!
But when I was using it, I noticed that the running memory on the server kept growing. I found a memory leak when using the tools "valgrind".
Does anyone else meet the same problem? Or just is the problem with the way I used it?
Many thanks !!

@MrIsland MrIsland reopened this Nov 24, 2021
@bbenligiray
Copy link
Owner

I'm not aware of such an issue and I suspect it would have already been raised. Leaving the issue open for others to comment.

@teigl
Copy link

teigl commented Jun 9, 2022

I faced the same issue. Found that the members EdgeMap and EDLines are not deleted when EDInterface is destroyed. This is also the case for fitPoints of customEllipse. The line is there in the destructor but it is commented out. Fixing these issues solved the memory leak issues for me but I have not tested with a memory checking tool like valgrind.
In addition, there are a few places where delete[] is used on a pointer allocated with malloc where free should be used (for instance in the destructor of customEllipse. Allocation of arrays with new is used many places but most places these are deleted with delete, not delete[], which could cause issues.

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

No branches or pull requests

3 participants