ember-cli: Production build errors
I am getting errors like this on 3.5.0-beta.2 and master branch when I run ember build -e production:
<--- Last few GCs --->
[16767:0x102801c00] 79950 ms: Mark-sweep 1384.2 (1424.9) -> 1383.9 (1425.4) MB, 1082.6 / 0.0 ms (average mu = 0.104, current mu = 0.006) allocation failure scavenge might not succeed
[16767:0x102801c00] 80916 ms: Mark-sweep 1385.0 (1425.9) -> 1384.8 (1426.9) MB, 960.0 / 0.0 ms (average mu = 0.059, current mu = 0.006) allocation failure scavenge might not succeed
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 0x1a57cbadc01d]
Security context: 0x10f298d9e681 <JSObject>
1: start [0x10f2197dd649] [/Users/rwwagner/shipshape/shipshape.io/node_modules/heimdalljs/dist/heimdalljs.cjs.js:~327] [pc=0x1a57cc3aaa14](this=0x10f2177858e1 <Heimdall map = 0x10f26969d271>,name=0x10f247075b81 <Object map = 0x10f23097a3e9>,Schema=0x10f25ed026f1 <undefined>)
2: arguments adaptor frame: 1->2
3: traverseTree(aka traverseTree) [0x10...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0x10003a08d node::Abort() [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
2: 0x10003a297 node::OnFatalError(char const*, char const*) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
3: 0x1001d2455 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
4: 0x10059d6d2 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
5: 0x1005a01a5 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
6: 0x10059c04f v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
7: 0x10059a224 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
8: 0x1005a6aac v8::internal::Heap::AllocateRawWithLigthRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
9: 0x1005a6b2f v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
10: 0x1005764b4 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
11: 0x1007fe234 v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/rwwagner/.nvm/versions/node/v10.11.0/bin/node]
12: 0x1a57cbadc01d
13: 0x1a57cc3aaa14
14: 0x1a57cba8a5a3
Output from ember version --verbose && npm --version && yarn --version:
ember-cli: 3.5.0-beta.2
http_parser: 2.8.0
node: 10.11.0
v8: 6.8.275.32-node.28
uv: 1.23.0
zlib: 1.2.11
ares: 1.14.0
modules: 64
nghttp2: 1.33.0
napi: 3
openssl: 1.1.0i
icu: 62.1
unicode: 11.0
cldr: 33.1
tz: 2018e
os: darwin x64
6.4.1
1.10.1
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 19 (17 by maintainers)
Commits related to this issue
- disable heimdall As sugested in https://github.com/ember-cli/ember-cli/issues/8118#issuecomment-430240755 — committed to buschtoens/broccoli by buschtoens 6 years ago
- Fix issue https://github.com/ember-cli/ember-cli/issues/8118 I'm not a fan of doing this here, it isn't actually representing what happens. I believe we should output the input ids on the node so yo... — committed to krisselden/broccoli by krisselden 6 years ago
- Merge pull request #379 from krisselden/fix-heimdall-graph Fix issue https://github.com/ember-cli/ember-cli/issues/8118 — committed to broccolijs/broccoli by rwjblue 6 years ago
https://github.com/broccolijs/broccoli/pull/379
Yeah I am investigating a recursive issue. It’s proving to be difficult. Will post updates as I find them
Digging into this further, it’s entering an endless loop, will report more when I know more.
Hmm, ok, i will do some digging