Sentry Vite Plugin reactComponentAnnotation causes Javascript Heap OOM

[mikehuebner]

Environment

• @sentry/vite-plugin -> ^2.22.7
• vite -> 6.0.3
• node -> 22.0.0

Steps to Reproduce

Build application with the following configuration

export default defineConfig({
  // ...
  plugins: [
    // ...
    sentryVitePlugin({
      org: 'cool-org-name',
      project: 'cooler-project-name',
      release: { name: `cooler-project-name@${Package.version}` },
      silent: true,
      reactComponentAnnotation: {
        enabled: true,
      },
    }),
  ]
});

Expected Result

A normal build, was working fine before the update to 2.22.7 I believe.

Actual Result

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

Things I've Tried

Adding NODE_OPTIONS="--max_old_space_size=8192" - can keep increasing as our runners use --max_old_space_size=10240

[AbhiPrasad]

Hey @mikehuebner thanks for writing in.

A normal build, was working fine before the update to 2.22.7 I believe.

What version were you using before 2.22.7?

Just to confirm, if you set reactComponentAnnotation. to false, you don't get errors anymore?

[mikehuebner]

Yup, false builds as normal! 2.22.4 was the previous version, along with vite: ^5

[lforst]

Since 2.22.4 we didn't really change anything that might be relevant to this issue. Do you think you would be able to provide a memory profile just so we can narrow down what happens to be consuming so much memory? 10 gigs seems excessive.

[mikehuebner]

Can do, I'll get that to you later this afternoon.

[erikian]

I've been also facing this issue with reactComponentAnnotation. It first started a couple of months ago with @sentry/[email protected], and an update to 2.22.5 solved it for a while, but recently it started failing again. Something between these versions must have improved memory usage (the only thing that catches my eye in the changelog is #598 which landed in 2.22.4), but I assume the issue reappeared as the codebase kept growing and the build started consuming more memory.

For context, I'm using Vite 4 and Node 22.

[lforst]

I unfortunately have to say this but it is basically impossible for us to investigate and debug OOM issues without consistent repro and/or memory profiles. If anybody could provide those I am happy to take a look!