Closed oopses closed 4 months ago
Hi, we can practically rule out that the webpack plugin is causing the OOM. It is more likely that Webpack is consuming a lot of memory generating sourcemaps.
You can try and exclude certain files from being sourcemapped in your build with webpack config, or provide your build server with more memory.
Hi, we can practically rule out that the webpack plugin is causing the OOM. It is more likely that Webpack is consuming a lot of memory generating sourcemaps.
You can try and exclude certain files from being sourcemapped in your build with webpack config, or provide your build server with more memory.
I closed the sentry sourcemap upload separately, and the packaging would not report an error
What do you mean by "closed" the upload?
What do you mean by "closed" the upload?
const sourcemaps = {
assets: ['dist/electron/*.js.map'],
ignore: ['node_modules'],
}
if(isProd){
sourcemaps.filesToDeleteAfterUpload = 'dist/electron/*.js.map'
}```
I changed the CLI on that device and uploaded it.
What do you mean by "closed" the upload?
const sourcemaps = { assets: ['dist/electron/*.js.map'], ignore: ['node_modules'], } if(isProd){ sourcemaps.filesToDeleteAfterUpload = 'dist/electron/*.js.map' }``` I changed the CLI on that device and uploaded it.
Found the problem. The problem should be in the Minified Scripts step, which caused the oom
node: 18.14.0 32 win10 webpack: 5.87.0 sentry/webpack-plugin: 2.14.1
build in jenkins,always prompt: