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.

Sign up for GitHub

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

Jump to bottom

Leak memory in current AST #11

Open
AJacques-UDS opened this issue Dec 4, 2022 · 0 comments
Open

Leak memory in current AST #11

AJacques-UDS opened this issue Dec 4, 2022 · 0 comments
Assignees
@AJacques-UDS
Labels
bug Something isn't working
Milestone
Abstract Syntax Tree

Comments

@AJacques-UDS
Copy link
Owner

Running vilgrind on PythonParser actually generates a lot of leak memory at end of application. This is probably due to the fact the AST is never destroyed. We will the need to actually complete it before continuing.
@AJacques-UDS AJacques-UDS added the bug Something isn't working label Dec 4, 2022
@AJacques-UDS AJacques-UDS added this to the Abstract Syntax Tree milestone Dec 4, 2022
@AJacques-UDS AJacques-UDS self-assigned this Dec 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AJacques-UDS AJacques-UDS

Labels
bug Something isn't working
Projects
None yet
Milestone
Abstract Syntax Tree
Development

No branches or pull requests
1 participant
@AJacques-UDS