Luca Forstner

@gffuma This actually helps a lot in narrowing down the problem. Thank you very much! That particular Next.js release [includes a PR that sounds like it could cause excessive memory...

@mosnicholas No update from our side. I'll ping Vercel about whether this issue has been fixed. It's best for you to just try things out on the newest Next.js version....

@mosnicholas you can upload source maps manually by following this guide: https://docs.sentry.io/platforms/javascript/sourcemaps/uploading/cli/ I think the memory consumption + long build time comes from the fact that source maps are generated....

@giankotarola Hi, building source maps is unfortunately relatively memory intensive. We don't do anything funky in the SDK besides turning on source map generation. You might want to raise this...

@MonstraG Please try to provide a memory profile for when this happens.

@johnsmith-gooddollar Would you be able to provide a reproduction example? Thanks!

@johnsmith-gooddollar Thank you! It looks like I don't have access to the repository you shared. Would you mind turning it public or adding me? Otherwise debugging this is gonna be...

@johnsmith-gooddollar What versions of your Sentry dependencies show in your lockfile? Can you try hardpinning the Sentry dependencies (ie removing `^`)? Thanks.

@johnsmith-gooddollar I am starting to run out of ideas... Does it also happen in an incognito tab without any browser extensions?

@johnsmith-gooddollar would you mind adding me to your repro repo so I can troubleshoot this?