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

Tokens created during evaluation not always destroyed #13

Open
Arc676 opened this issue Jun 23, 2018 · 0 comments
Open

Tokens created during evaluation not always destroyed #13

Arc676 opened this issue Jun 23, 2018 · 0 comments
Labels
bug Something isn't working
Milestone
Memory issues

Comments

@Arc676
Copy link
Owner

Arc676 commented Jun 23, 2018 •
edited
Loading

When evaluating blocks and loops, the evaluated values are assigned to the overall return value but intermediate values are not destroyed properly.

evaluation.c, line 254 as at commit 30376cd

returnValue = eval(statements[i], childScope);

This memory leak should be fixed.
@Arc676 Arc676 added the bug Something isn't working label Jun 23, 2018
@Arc676 Arc676 added this to the Memory issues milestone Jun 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
Memory issues
Development

No branches or pull requests
1 participant
@Arc676