You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prior to this bug report, I've opened an issue on the sass-embedded board and it was suggested that it might be related to how sass-loader handles sass-embedded.
I am using sass-embedded alongside sass-loader in my webpack config.
I've noticed, that when running out of memory and physical memory the dart processes throws errors and stop.
Actual Behavior
Webpack doesn't crash and exit, but there are dart errors printed out and the compilation stops.
It was suggested that it might be due to sass-loader spawning many instances of sass-embedded, maybe sass-loader should be more conservative when using resources?
I run two sass-loader instances in parallel to compile two sections of a pretty big codebase of sass.
To reproduce this problem it is necessary to exceed the system memory, in my case I went above 6-8 GB out of 16 GB. It is also necessary to not have much physical memory available. I had something near 500-250 MB.
Please paste the results of npx webpack-cli info here, and mention other relevant information
Should be fixed by #1199, please update sass-loader to the latest stable versiob, i.e. 14.2.1, if it will not fix your problem need to wait an answer from sass-embedded, so feel free to feedback
According to my webpack-cli info, I believe I have 14.2.1 installed.
That aside, I have a question,
Looking at the commit there's a comment that says it should handle multi-threading more gracefully.
Does multi-threading mean the way of using webpack when the module exports multiple configurations?
If that's it it's how I am currently using webpack for running multiple configurations.
Bug report
Prior to this bug report, I've opened an issue on the sass-embedded board and it was suggested that it might be related to how sass-loader handles sass-embedded.
sass/embedded-host-node#296 (comment)
I am using sass-embedded alongside sass-loader in my webpack config.
I've noticed, that when running out of memory and physical memory the dart processes throws errors and stop.
Actual Behavior
Webpack doesn't crash and exit, but there are dart errors printed out and the compilation stops.
Expected Behavior
It was suggested that it might be due to sass-loader spawning many instances of sass-embedded, maybe sass-loader should be more conservative when using resources?
How Do We Reproduce?
This is my sass-loader config:
I run two sass-loader instances in parallel to compile two sections of a pretty big codebase of sass.
To reproduce this problem it is necessary to exceed the system memory, in my case I went above 6-8 GB out of 16 GB. It is also necessary to not have much physical memory available. I had something near 500-250 MB.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationI am running windows and using:
webpack 5.91.0
sass-loader 14.2.1
sass-embedded 1.77.0
npx webpack-cli info:
The text was updated successfully, but these errors were encountered: