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
{{ message }}
Repository navigation
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory #3
When I try to minify large (several MB), I get the following error:
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
googleing around shows that this seems to happen when node is running code with memory leaks. Indeed, the node process running ycssmin uses >600MB memory prior to erroring.
Anything I can do to identify the source of the memory leak?
The file is ~5MB. This is a company CSS file, so I can't post a dump of it :(
However, I found I could reproduce the problem by duplicating a 100kb or so of CSS repeatedly in the same file.
@hbmartin Not sure if you solved this issue, but we ran into it yesterday.
Just now we've discovered that for us the issue was with having less generate comments.
We were checking the memory size of the node process during execution, and with comments generation turned on, the process hit 1.2GB and blew up. When we removed comment generation, the same process topped out around 55 megs.
I'll just chime on in, nigh 2 years later, that I was having the same error and turning off line comments in compass (my CSS preprocessor) fixed the issue as well.
Activity
davglass commentedon Feb 13, 2013
How big is this CSS file? Can I get a copy to test it with?
hbmartin commentedon Feb 13, 2013
The file is ~5MB. This is a company CSS file, so I can't post a dump of it :(
However, I found I could reproduce the problem by duplicating a 100kb or so of CSS repeatedly in the same file.
davglass commentedon Feb 13, 2013
I'll take a look at this sometime tomorrow.
erichmond commentedon Jul 18, 2013
@hbmartin Not sure if you solved this issue, but we ran into it yesterday.
Just now we've discovered that for us the issue was with having less generate comments.
We were checking the memory size of the node process during execution, and with comments generation turned on, the process hit 1.2GB and blew up. When we removed comment generation, the same process topped out around 55 megs.
Hope this helps!
jeremybmerrill commentedon May 29, 2015
I'll just chime on in, nigh 2 years later, that I was having the same error and turning off line comments in
compass(my CSS preprocessor) fixed the issue as well.