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

tsup OOM Error #208

Open
jutrec opened this issue Jun 21, 2024 · 0 comments
Open

tsup OOM Error #208

jutrec opened this issue Jun 21, 2024 · 0 comments

Comments

@jutrec
Copy link

jutrec commented Jun 21, 2024

Using tsup to build our app, we see a huge memory leak in the process.

Locally, the node.js JavaScript Runtime gets increasingly bigger until it reaches 4GB of Memory, and then it crashed. The crash occurs in 30sec to 1 minute after launching the app, and doing nothing at all with it.
image

In the CI pipeline, we increased the max memory size to 8GB using NODE_OPTIONS: --max_old_space_size=8192, which did the job...

We have been experimenting with using the tsup --experimental-dts to replace the normal --dts. So far, the app memory is stable around 600MB locally, and build 3 times faster in the CI pipeline (30s, down from 1min30s).

So far, no issues with the new tsup config. We will continue to monitor the effects of the new config.

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