Recently, when I was writing a project based on angular4, I suddenly caught off guard and reported an error, with the following error:
70% building modules 1345/1345 modules 0 active <--- Last few GCs ---> ms: Mark-sweep 703.9 (837.9) -> 701.4 (811.9) MB, 331.3 / 0 ms [allocation failure] [GC in old space requested]. ms: Mark-sweep 701.4 (811.9) -> 701.4 (790.9) MB, 350.5 / 0 ms [allocation failure] [GC in old space requested]. ms: Mark-sweep 701.4 (790.9) -> 698.0 (760.9) MB, 433.7 / 0 ms [last resort gc]. ms: Mark-sweep 698.0 (760.9) -> 692.7 (751.9) MB, 328.7 / 0 ms [last resort gc]. <--- JS stacktrace ---> ==== JS stack trace ========================================= Security context: 00000298510373A9 <JS Object> 1: /* anonymous */(aka /* anonymous */) [D:\dev\cobalt_wp\node_modules\webpack\lib\:77] [pc=0000026F721B51D6] (this=0000029851004131 <undefined>,dep=00000150FC6162C9 <a NormalModule with map 0000025741730C01>) 2: arguments adaptor frame: 3->1 3: InnerArrayForEach(aka InnerArrayForEach) [native :~924] [pc=0000026F71EE3DCD] (this=000002985100413... FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Note: The code here is not my real error reporting code. The compilation time is too long and I forgot to intercept it. The general error is basically the same. If you encounter the same problem, congratulations. You can find the answer after reading it down!
I was confused at that time and I had been compiling well all the time, why did it suddenly overflow?
Possible reasons are as follows:
1. When angular4 is compiled, the CPU and memory demand is relatively large. When the number of files is large, there may be insufficient memory (possible);
2. When the code has a large number of big data loops or dead loops (there is no overflow during the sever stage, the probability should be small);
Subscribed data is not destroyed during the ngOnDestroy stage, causing a large amount of data to occupy memory (possible)
No specific reason was found at present. Which master knows? Please give me advice, thank you!
The process of solving this problem is very twists and turns, so I won’t talk about it here. You probably don’t want to know it. Let’s talk about the solution below:
The core idea is to use the old attributes of the v8 engine: --max_old_space_size to modify the memory and go online. As for where to set this attribute, it is a scheming little goblin!
Modify the directory: my-project/node_modules/.bin Found:
@IF EXIST "%~dp0\" ( "%~dp0\" --max_old_space_size=8192 "%~dp0\..\._@[email protected]@@angular\cli\bin\ng" %* ) ELSE ( @SETLOCAL @SET PATHEXT=%PATHEXT:;.JS;=;% node --max_old_space_size=8192 "%~dp0\..\._@[email protected]@@angular\cli\bin\ng" %* )
Modify the directory: my-project/node_modules/.bin Found:
@IF EXIST "%~dp0\" ( "%~dp0\" --max_old_space_size=8192 "%~dp0\..\._@[email protected]@@angular\compiler-cli\src\" %* ) ELSE ( @SETLOCAL @SET PATHEXT=%PATHEXT:;.JS;=;% node --max_old_space_size=8192 "%~dp0\..\._@[email protected]@@angular\compiler-cli\src\" %* )
Have you seen the --max_old_space_size set in it? As for the number you set, you can do it yourself. My project is relatively large, set a larger value in case of accidents, haha!
Then execute ng build --prod , do you think this is enough? This is the key point!
I personally test it. As set above, if you execute the compilation, it will still report memory overflow, which seems to be useless! Switch the current directory to my-project/node_modules/.bin and then execute ng build --prod, and the world will be peaceful all of a sudden! I personally test it effectively, I will be very grateful!
If you want to ask, why not add --aot, leave this for yourself and think about it first!
Okay, I'll take some time off and share the method of filling this big pit, hoping it will be useful to everyone!
The above is all the content of this article. I hope it will be helpful to everyone's study and I hope everyone will support me more.