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

Compiling large libraries uses far too much RAM. #2686

Open
otrho opened this issue Sep 1, 2022 · 0 comments
Open

Compiling large libraries uses far too much RAM. #2686

otrho opened this issue Sep 1, 2022 · 0 comments
Labels
bug Something isn't working compiler: frontend Everything to do with type checking, control flow analysis, and everything between parsing and IRgen P: medium

Comments

@otrho
Copy link
Contributor

otrho commented Sep 1, 2022

As noted in #2674 (comment) when compiling large libraries with several deps in lib.sw we can use a metric tonne of RAM.

I have a feeling we're just leaking a whole lot of intermediate data structures which could be dropped between compiling each dep, but a proper investigation should be made.
@otrho otrho added bug Something isn't working compiler: frontend Everything to do with type checking, control flow analysis, and everything between parsing and IRgen labels Sep 1, 2022
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 compiler: frontend Everything to do with type checking, control flow analysis, and everything between parsing and IRgen P: medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@otrho @mohammadfawaz