Vulnerability Summary for the Week of September 17, 2018 | CISA test: /\.(woff(2)?|ttf|eot|otf)(\?v=\d+\.\d+\.\d+)?$/. extra info: I too facing the same issue with the latest webpack. My first question: what does the number 1829 (and 2279) represents exactly ? If this generates many files in to your output path, the webpack-dev-server generates many files in the memory-fs. Well, It will be nearly impossible to help you without the config. Gotcha, can confirm it persists after updating as well. Uncaught TypeError: (0 , vue__WEBPACK_IMPORTED_MODULE_20__.reactive) is not a function - in Vue 2 2 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory error Command failed with exit code 134. This is vague - what version of postcss-loader has the memory leak? This mode will minimize memory usage but introduce a performance cost. cache.maxMemoryGenerations: 1: This will purge items from the memory cache once they are serialized and unused for at least one compilation. 12: 00007FF7B187E602 v8::internal::Factory::NewFixedArrayWithFiller+66 path: /api/alexa/petrolstationslocation/{fueltype}/{brand}/{offset}/{miles}/{sort} Fatal error call and retry last allocation failed process out of memory cache.managedPaths is an array of package-manager only managed paths. My build is not passing through CI and I do not want to go back to https://github.com/prisma/serverless-plugin-typescript because it is using an outdated version of typescript and appears to be looking for maintainers. Previously, we were on webpack 3.12.0 and webpack-dev-server 2.11.3, and now we're on webpack 4.22.0 and webpack-dev-server 3.1.10. Then do a serverless package to test, if it works. Any hints how to optimize memory consumtion for sourcemap creation? FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory, FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory. I had to give up on webpack-dev-server because it crashed on the first code change every single time. [17208:0000020B4EB70F20] 1184996 ms: Scavenge 3365.3 (4162.0) -> 3364.3 (4162.5) MB, 10.8 / 0.0 ms (average mu = 0.164, current mu = 0.189) allocation failure Disabling sourcemaps helps, but can't be a solution. target: 'node', Vue.jsLaravel Vue This is further confirmed when tested with thread-loader, the timer increases individually in each thread. If youre using Bash, then add the following line to your .bashrc file:if(typeof ez_ad_units != 'undefined'){ez_ad_units.push([[250,250],'sebhastian_com-large-mobile-banner-1','ezslot_4',143,'0','0'])};__ez_fad_position('div-gpt-ad-sebhastian_com-large-mobile-banner-1-0'); When youre using ZSH, then add the line above to the .zshrc file. [1] 28586 abort ./bin/webpack-dev-server, ActionText: All the ways to render an ActionText Attachment, ActionText: Safe listing attributes and tags, ActionText: Modify the rendering of ActiveStorage attachments. - sg-0a328af91b6508ffd My educated guess is that packages in node_modules contains side effects that webpack has no way to cleanup after bundling.