ember-cli / ember-cli/stress-app
Node runs out of memory during production build
- Dominant language
- HTML
- Stars
- 9
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
From a clean clone, running `ember build --environment=production` yields the following error:
``` bash
<--- Last few GCs --->
151400 ms: Scavenge 1394.2 (1456.9) -> 1394.2 (1456.9) MB, 0.9 / 0 ms (+ 5.6 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
152541 ms: Mark-sweep 1394.2 (1456.9) -> 1254.8 (1456.9) MB, 1141.6 / 0 ms (+ 9.9 ms in 3 steps since start of marking, biggest step 5.6 ms) [last resort gc].
154054 ms: Mark-sweep 1254.8 (1456.9) -> 1254.7 (1456.9) MB, 1512.8 / 0 ms [last resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x2259336e3ac1
1: has_side_effects [0x225933604189 :~5889] [pc=0x328e06438e03] (this=0x38dfe0a110e9 ,compressor=0x2f16a43053c9 )
2: /* anonymous */(aka /* anonymous */) [0x225933604189 :6042] [pc=0x328e065f9b07] (this=0x225933604189 ,def=0x2851bf7f59c1 )
...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Abort trap: 6
```
However, a development `ember build` completes rather quickly without any issues.
We have been seeing this issue occur with our large application as well, which is why I cloned the stress-app in the first place. My gut instinct is that the Uglify process (which seems to be one of the few diffs between development and production builds) doesn't handle exceedingly large (> 8 mb or so) JS files.
Here's some relevant environment info as well:
``` bash
ember --version
ember-cli: 2.5.0
node: 5.4.0
os: darwin x64
```
cc @chadhietala
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.