-
Notifications
You must be signed in to change notification settings - Fork 53
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 leaks after a compiler error #212
Comments
@ProkopRandacek I suppose #211 and #212 are in fact the same issue. Error handling in Umka is based on |
To battle that problem, somewhere in compiler you can store a list of pointers you malloc'd, then just free them all upon an error |
Example input:
The second lexer that is created for the file
th.um
is not freed when the compiler exits later because of the invalid syntax.Leak sanitizer backtrace:
the first leak in
parseImportItem
is already reported in #211The text was updated successfully, but these errors were encountered: