<--- Last few GCs --->
45903 ms: Mark-sweep 1385.6 (1438.9) -> 1385.6 (1438.9) MB, 742.8 / 0.0 ms (+ 0.8 ms in 1 steps since start of marking, biggest step 0.8 ms) [allocation failure] [GC in old space requested].
46512 ms: Mark-sweep 1385.6 (1438.9) -> 1387.3 (1422.9) MB, 607.4 / 0.0 ms (+ 0.8 ms in 1 steps since start of marking, biggest step 0.8 ms) [last resort gc].
47111 ms: Mark-sweep 1387.3 (1422.9) -> 1389.5 (1422.9) MB, 599.6 / 0.0 ms [last resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x1c6b6bcfb51 <JS Object>
1: deserializeObject(aka deserializeObject) [/home/ubuntu/veerendergoudapi/node_modules/bson/lib/bson/parser/deserializer.js:~41] [pc=0x1a9fab83915a] (this=0x1c6b6b04381 <undefined>,buffer=0x193d54f18579 <an Uint8Array with map 0xd4eba2066c9>,index=0,options=0x1e11b6cedfc9 <an Object with map 0x19eb230b3809>,isArray=0x1c6b6b04381 <undefined>)
2: deserialize(aka deserialize) [/home/ubuntu...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [node]
2: 0x10a3b3c [node]
3: v8::Utils::ReportApiFailure(char const*, char const*) [node]
4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
5: v8::internal::Factory::NewTransitionArray(int) [node]
6: v8::internal::TransitionArray::Insert(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::Map>, v8::internal::SimpleTransitionFlag) [node]
7: v8::internal::Map::CopyReplaceDescriptors(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::DescriptorArray>, v8::internal::Handle<v8::internal::LayoutDescriptor>, v8::internal::TransitionFlag, v8::internal::MaybeHandle<v8::internal::Name>, char const*, v8::internal::SimpleTransitionFlag) [node]
8: v8::internal::Map::CopyAddDescriptor(v8::internal::Handle<v8::internal::Map>, v8::internal::Descriptor*, v8::internal::TransitionFlag) [node]
9: v8::internal::Map::CopyWithField(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::FieldType>, v8::internal::PropertyAttributes, v8::internal::Representation, v8::internal::TransitionFlag) [node]
10: v8::internal::Map::TransitionToDataProperty(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::StoreFromKeyed) [node]
11: v8::internal::LookupIterator::PrepareTransitionToDataProperty(v8::internal::Handle<v8::internal::JSObject>, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::StoreFromKeyed) [node]
12: v8::internal::Object::AddDataProperty(v8::internal::LookupIterator*, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::ShouldThrow, v8::internal::Object::StoreFromKeyed) [node]
13: v8::internal::Object::SetProperty(v8::internal::LookupIterator*, v8::internal::Handle<v8::internal::Object>, v8::internal::LanguageMode, v8::internal::Object::StoreFromKeyed) [node]
14: v8::internal::Runtime::SetObjectProperty(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::LanguageMode) [node]
15: v8::internal::Runtime_SetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [node]
16: 0x1a9faac092a7
error: Forever detected script was killed by signal: SIGABRT
error: Script restart attempt #571
几天前,当我们的应用程序处于生产阶段,大约有200个活跃用户时,我们也面临过类似的问题。整个应用程序因此而宕机。经过几个小时的调试,我们发现其中一个API没有将正确的错误对象传递给环回远程方法回调。
环回要求错误对象为[格式][1]
{status:<some statuscode>, message:<error message>, name:<name for the error>}
我们给它传递了一个真正的例外,一切都变得混乱了。在推动此修复后,泄漏和错误已经消失。
node --max-old-space-size=4096 file.js
我正在使用Lambda(nodeJS)查询noSQL数据(dynamo db)。 null 我犯了错误: 42676 ms:标记-扫描804.1(954.3)->802.7(954.3)MB,1803.0/0.0ms(标记开始后32步+246.3ms,最大步35.7ms)[分配失败][请求旧空间中的GC]。44415 ms:标记-扫描802.7(954.3)->802.7(954.3)MB,173
<---JS StackTrace---> =====JS栈迹=================================================================== 安全上下文:0369632D1:create(This=036856A9)2:_Walk[034841A1:~764][PC=1CCAED1F](This=3A11A619,Visitor=3BCEFD
我试图用AOT构建我的angular-cli项目 你知道吗?
我还试图解决这里建议的问题,如何修复“致命错误:无效标记-压缩接近堆限制分配失败-JavaScript堆出内存”错误,但对我来说不起作用 这是我的package.json
问题内容: 节点版本为 崩溃期间的内存使用情况未超出 产生此错误的代码: 要检查是否存在递归堆栈大小问题,我使用–stack-size = 60000参数运行了下一个代码 并得到了 然后,我运行了导致严重错误的代码:CALL_AND_RETRY_LAST分配失败-使用相同的–stack-size = 60000参数处理内存不足,并且没有得到。 因此,我得出结论与递归堆栈大小没有共同之处。 我该如何