sentry-javascript-bundler-plugins: sentry-vite-plugin cause javascript out of memory

Here is the reproducible example - sovereign-nature/deep@main/apps/verification-portal/vite.config.ts. Just uncomment sentry lines and the build process will stuck after source maps upload.

@smakhtin Big. Thank you! We will take a look!

@GreenbowAllan We have no reason to believe it is @sentry/vite-plugin causing the oom issues but rather vite itself (or other plugins) consuming a lot of memory when generating or emitting source maps.

If you want to contribute to this you could share a heap profile of your builds when they oom.

Okay, I’m gonna go ahead and close this issue. For anybody running into this, it seems like the best solution is to upgrade vite to version 4.4.9 and @sentry/vite-plugin to version 2.16.1. Both packages introduced performance/memory consumption improvements in those versions. Feel free to ping me here if you have any new findings (in case the issue persists)!

Hello @getsentry team and fellow developers,

I’ve been following this thread with interest, as I am encountering a similar issue with the Sentry Vite plugin in a Nuxt 3 project. Specifically, enabling the plugin with source map generation leads to an OOM error in our Jenkins/Docker build pipeline, significantly affecting our CI/CD processes.

Has there been any progress or potential workarounds identified since the last update? I’ve noticed that increasing the memory allocation for Node.js has been a temporary fix for some, but it’s not a viable long-term solution for us due to the constraints of our build environment.

Additionally, if there’s any specific information or debugging data that could help in diagnosing this issue further, please let me know. I’m eager to contribute to finding a solution that helps not just our project but others facing similar challenges.

Thank you for your efforts and any guidance you can provide.

Here is the reproducible example - https://github.com/sovereign-nature/deep/blob/main/apps/verification-portal/vite.config.ts. Just uncomment sentry lines and the build process will stuck after source maps upload.

I do not have a reproducible example at this time but I can confirm that the issue only occurs when we add the @sentry/vite-plugin to our build.

The build succeeds when generating source maps without the sentry plugin. We tried using a custom plugin to exclude node_modules from sourcemaps; again the build succeeds w/o @sentry/vite-plugin but fails due to OOM error with the sentry plugin. Our build is only 87MB and we allocate 4GB for the build node process and still do not have enough memory when the sentry plugin is included in the build.

I’m starting to read through the plugin source code and will update if I find anything suspicious.

Update:

Increasing --max-old-space-size by 75% to 7GB still fails when the @sentry/vite-plugin is included in the build

Hi all, we just released version 2.16.1 of the package. Can you try whether upgrading fixes the issue for you? (🤞)

the issue is usually because of sourcemaps for large files for me issue was solved by manually creating chunks and making the main vendor file smaller

rollupOptions: {
        output: {
          manualChunks: (id) => {
            if (id.includes(X)) {
              return "vendor-X";
            }
             if (id.includes(Y)) {
              return "vendor-Y";
            }
          },
}

Experiencing the same problem if somebody found a solution…

Turns out it was the vite build that was failing with OOM when generating the source maps even if I removed the Sentry plugin from the equation, thus not related to this project. I excluded “node_modules” and everything went fine.

For our CI it was also fixed by updating @sentry/vite-plugin from 2.16.0 to 2.16.1

After producing (seemingly) no useful output with the profiler I branched out to maybe produce some useful information and alas:

• I still got OOM errors with the sentry plugin disabled, however they were a lot easier to reproduce with the plugin enabled. Maybe the plugin was the last drop in the heap-bucket (at least in our case)
• Since this now seemed much more likely to be on vite / rollup’s end, I updated vite to the most recent 5.2.8 and I cannot reproduce the OOM locally (which I could with almost 100% rate on vite@4.4.7) - My guess is that this comes from https://github.com/vitejs/vite/pull/14016 which states in the PR description “I’ve seen around 28% faster builds, with a 1.3 GB (36.6%) reduction in peak memory usage”; I could also not reproduce OOMs with vite@4.4.9 which that PR landed in.

So TL;DR: Not sentry-vite-plugin’s fault after all?

Is there a way to fix this issue?

As far as I know - no. Vendor bundle isolation helped me, but caused other bugs with caching, so now I just disabled source maps. Very annoying bug.

I think i can confirm it that bundle size was causing this error. I isolated vendor bundle and everything works again.

I just run into it as well when trying to setup vite plugin using sentry wizzard.

sourcemap enabled and sentryVitePlugin

> vite build

[sentry-vite-plugin] Info: Using environment variables configured in ".env.sentry-build-plugin".
vite v4.5.0 building for production...
[sentry-vite-plugin] Info: Sending error and performance telemetry data to Sentry. To disable telemetry, set `options.telemetry` to `false`.
node_modules/flexsearch/dist/flexsearch.bundle.js (23:33) Use of eval in "node_modules/flexsearch/dist/flexsearch.bundle.js" is strongly discouraged as it poses security risks and may cause issues with minification.
✓ 5595 modules transformed.

rendering chunks (3)...
<--- Last few GCs --->

[8023:0x128078000]    33282 ms: Scavenge (reduce) 4027.0 (4142.2) -> 4026.7 (4142.7) MB, 5.0 / 0.0 ms  (average mu = 0.432, current mu = 0.303) allocation failure;
[8023:0x128078000]    35495 ms: Mark-sweep (reduce) 4028.4 (4144.0) -> 4028.2 (4144.7) MB, 1963.7 / 0.0 ms  (average mu = 0.253, current mu = 0.131) allocation failure; GC in old space requested


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x10492fc40 node::Abort() [/Users/kes/.nvm/versions/node/v18.18.2/bin/node]

sourcemap enabled, without sentryVitePlugin

> vite build

vite v4.5.0 building for production...
node_modules/flexsearch/dist/flexsearch.bundle.js (23:33) Use of eval in "node_modules/flexsearch/dist/flexsearch.bundle.js" is strongly discouraged as it poses security risks and may cause issues with minification.
✓ 5594 modules transformed.
✓ built in 31.12s
npm run build  94.37s user 8.39s system 321% cpu 31.921 total

Increasing max memory used to 8GB worked.

> NODE_OPTIONS=--max-old-space-size=8192 vite build

[sentry-vite-plugin] Info: Using environment variables configured in ".env.sentry-build-plugin".
vite v4.5.0 building for production...
[sentry-vite-plugin] Info: Sending error and performance telemetry data to Sentry. To disable telemetry, set `options.telemetry` to `false`.
node_modules/flexsearch/dist/flexsearch.bundle.js (23:33) Use of eval in "node_modules/flexsearch/dist/flexsearch.bundle.js" is strongly discouraged as it poses security risks and may cause issues with minification.
✓ 5595 modules transformed.

....
build/assets/index-a34f4e16.js                                              64.95 kB │ gzip:    23.33 kB │ map:    251.61 kB
build/assets/index-f8a37c58.js                                           8,620.20 kB │ gzip: 2,565.32 kB │ map: 24,272.34 kB

(!) Some chunks are larger than 500 kBs after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
> Found 6 files
> Analyzing 6 sources
> Analyzing completed in 0.116s
> Adding source map references
> Bundling completed in 1.123s
> Bundled 6 files for upload
> Bundle ID: e0e63b40-801d-55ad-84f2-6f2915bab739
> Optimizing completed in 0.046s
> Uploading completed in 3.325s
> Uploaded files to Sentry
> Processing completed in 0.399s
> File upload complete (processing pending on server)
...
> Release: ea04fb85188d79e46c700fb306c08be004f1a3f5
> Dist: None
> Upload type: artifact bundle

[sentry-vite-plugin] Info: Successfully uploaded source maps to Sentry
✓ built in 44.95s
npm run build  102.16s user 12.67s system 249% cpu 46.052 total

We do have relatively large code base, so not quite sure , but based on monitoring, it peak above 5GB before finishing.

What is interesting is that when enabled, the transformed module count increased from 5594 modules transformed. to 5595 modules transformed.