Open alirzayev-clopos opened 1 week ago
Note: if I increase heap size with this command, it runs successfully. But I don't think that's a solution as it should be ok to run in low-memory servers like Github Actions.
NODE_OPTIONS=--max-old-space-size=14096 vite build
hey @alirzayev-clopos thanks for writing in.
this is probably related to https://github.com/getsentry/sentry-javascript-bundler-plugins/issues/512
Could you please check this issue and see if any of the hints there might resolve your problem?
Hey @chargome.
Yes, I have read that issue and they are related. But hints don't solve my problem.
sourcemap: true
without Sentry plugin builds successfully.I will export memory profile and provide.
I have captured the memory profile, and ironically, it finished build successfully. I guess profiler does not limit heap size, that's why it succeeds.
I can't share a memory profile as it contains source code which I don't have rights to share.
@alirzayev-clopos thanks for that, when you inspect the profile, can you spot anything that seems way off that could give us a hint?
@chargome, unfortunately no. Sizes seem too big but don't know if it is a problem. How can I help to solve this problem? Should I provide something else?
@alirzayev-clopos without us inspecting the memory profile or creating a reproducible repo we cannot really debug this from our side I'm afraid.
Okay. I will try my best to create a reproducible repo.
Environment
Instance: self-hosted
vite.config.ts:
Steps to Reproduce
tsc && vite build
Expected Result
Sourcemaps uploaded to sentry.
Actual Result