-
Notifications
You must be signed in to change notification settings - Fork 12k
Memory Leak when using ng #17022
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you try using Node v12.4.0+? There are some node versions that suffer from memory issues. |
I've uninstalled node v13.8.0 and installed node v12.16.1 I have a war machine under my control and still can't control JavaScript related tools 🤣 With
With
|
@eau-de-la-seine, is there anyway that you can share your project so that we can take a look at this issue?, even privately. |
I would have love to but I cannot send this company project. Anyway I've found a solution: remove the whole project and clone it again, now it works. This is still weird to me since the source code wasn't changed and even |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Hi,
There's a memory leak with
ng
, it keeps consuming memory despite memory increase, I've monitored and it has already consumed more than 17 GB of RAM! I think the problem is related to SASS because the program is stucked with.scss
files but I'm not sure.I've tested with
NODE_OPTIONS=--max-old-space-size=17000
but alsonode --max_old_space_size=20000 node_modules/@angular/cli/bin/ng build --prod
later, always the same issue even if I try with8192
instead of17000
or20000
.I know, this memory problem has already been opened multiple times, like here #13734, but it seems to be a persistent issue
Terminal
Generated JSON report
Softwares
My computer
The text was updated successfully, but these errors were encountered: