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

Test for source_map memory leaks #12

Open
ef4 opened this issue Jul 12, 2023 · 0 comments
Open

Test for source_map memory leaks #12

ef4 opened this issue Jul 12, 2023 · 0 comments

Comments

@ef4
Copy link
Collaborator

ef4 commented Jul 12, 2023

I am reasonably confident that the span interning system in swc is going to hold onto an ever-growing amount of data if you continuously do rebuilds using the same Preprocess instance.

But every example in swc itself that I can find also does things that way. swc holds the source maps in a static lifetime and calls new_source_file again and again on it, which is equivalent to what we're doing.

It would be good for someone to exercise this on a bigger build and watch the memory consumption as soon as we have it wired into a useful system.

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

1 participant