You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: