Lastly, I use ember to develop. But I found it strange that when I installs packages like the following order: npm install
and then bower install
, it caused the out of memory exception; and when I exchange the order, it works well. The exception is as follows:
WARNING: Node v8.1.2 has currently not been tested against Ember CLI and may result in unexpected behaviour.
<--- Last few GCs --->
[5015:0x102805200] 74556 ms: Mark-sweep 1404.9 (1464.9) -> 1404.8 (1439.9) MB, 2781.4 / 0.0 ms (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 2781 ms) last resort
[5015:0x102805200] 77514 ms: Mark-sweep 1404.8 (1439.9) -> 1404.8 (1439.9) MB, 2957.7 / 0.0 ms last resort
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x10d601fa9891 <JS Object>
3: keysForTree [/Users/gpc/Documents/codes/gitlab/sixtant-fornt/sixtant/node_modules/.0.3.1@broccoli-kitchen-sink-helpers/index.js:36] [bytecode=0x15fbb22b08a9 offset=63](this=0x2a2411a8b051 <JS Global Object>,fullPath=0x1e708a1f0629 <String[860]: /Users/gpc/Documents/codes/gitlab/sixtant-fornt/sixtant/node_modules/.6.0.0@broccoli-babel-transpiler/node_modules/babel-core/node_modules/babel-...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [/usr/local/bin/node]
2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
4: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
5: v8::internal::Factory::NewScopeInfo(int) [/usr/local/bin/node]
6: v8::internal::ScopeInfo::Create(v8::internal::Isolate*, v8::internal::Zone*, v8::internal::Scope*, v8::internal::MaybeHandle<v8::internal::ScopeInfo>) [/usr/local/bin/node]
7: v8::internal::Scope::AllocateScopeInfosRecursively(v8::internal::Isolate*, v8::internal::MaybeHandle<v8::internal::ScopeInfo>) [/usr/local/bin/node]
8: v8::internal::DeclarationScope::AllocateVariables(v8::internal::ParseInfo*, v8::internal::AnalyzeMode) [/usr/local/bin/node]
9: v8::internal::DeclarationScope::Analyze(v8::internal::ParseInfo*, v8::internal::AnalyzeMode) [/usr/local/bin/node]
10: v8::internal::Compiler::Analyze(v8::internal::ParseInfo*, v8::internal::ThreadedList<v8::internal::ThreadedListZoneEntry<v8::internal::FunctionLiteral*> >*) [/usr/local/bin/node]
11: v8::internal::(anonymous namespace)::GetOptimizedCode(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Compiler::ConcurrencyMode, v8::internal::BailoutId, v8::internal::JavaScriptFrame*) [/usr/local/bin/node]
12: v8::internal::Compiler::CompileOptimized(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Compiler::ConcurrencyMode) [/usr/local/bin/node]
13: v8::internal::Runtime_CompileOptimized_Concurrent(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
14: 0x253ed080437d
[1] 5015 abort ember s
And the node version is v8.1.2, npm version is 5.0.3.
By the way, when the node version is v5.5.0, the exception is as follows:
So why? Is bower and npm independent? Why the OOM happens?
Aucun commentaire:
Enregistrer un commentaire