weixin_39631953
weixin_39631953
2020-11-29 23:15

[V2 rc0] RangeError: Maximum call stack size exceeded

Multiple people are getting below arrors. Originally I opened an issue abut it for ionic repository abut i beilive ionic-cli is more appropriate place for it:

https://github.com/driftyco/ionic/issues/8280

Stack:


[00:52:28]  RangeError: Maximum call stack size exceeded
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:153:20)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)
    at deepClone (/Users/barbarian/TS/greenkey/greenkey-tabs-rc0/node_modules/rollup/dist/rollup.js:165:18)

And also this error is thrown frequently:


[08:36:53]  bundle dev update started ...

 3466571 ms: Mark-sweep 1274.0 (1435.0) -> 1272.4 (1435.0) MB, 1445.4 / 0 ms [allocation failure] [GC in old space requested].
 3468039 ms: Mark-sweep 1272.4 (1435.0) -> 1272.4 (1435.0) MB, 1467.7 / 0 ms [allocation failure] [GC in old space requested].
 3469589 ms: Mark-sweep 1272.4 (1435.0) -> 1272.4 (1435.0) MB, 1549.6 / 0 ms [last resort gc].
 3471091 ms: Mark-sweep 1272.4 (1435.0) -> 1272.4 (1435.0) MB, 1502.6 / 0 ms [last resort gc].

==== JS stack trace =========================================
Security context: 0x361bce9c9e31 <js object>
    1: Join(aka Join) [native array.js:179] [pc=0x4b0bbe181f5] (this=0x361bce904189 <undefined>,w=0x1905f65f2399 <js array>,x=94699,N=0x89790b28e99 <string>,M=0x361bce9b4ab1 <js function converttostring>)
    2: InnerArrayJoin(aka InnerArrayJoin) [native array.js:~343] [pc=0x4b0bce12b6c] (this=0x361bce904189 <undefined>,N=0x89790b28e99 <string fatal error: call_and_retry_last allocation failed javascript heap out of memory node::abort node::fatalexception v8::local>, v8::Local<:message>)
 [/usr/local/Cellar/node/6.3.1/bin/node]
 3: 
v8::Utils::ReportApiFailure(char const*, char const*) [/usr/local/Cellar/node/6.3.1/bin/node]
 4: 
v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/Cellar/node/6.3.1/bin/node]
 5: 
v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/usr/local/Cellar/node/6.3.1/bin/node]
 6: 
v8::internal::Runtime_StringBuilderJoin(int, v8::internal::Object**, v8::internal::Isolate*)
 [/usr/local/Cellar/node/6.3.1/bin/node]

</:message></string></undefined></js></string></js></undefined></js>

Cordova CLI: 6.3.1
Gulp version:  CLI version 1.2.2
Gulp local:  
Ionic Framework Version: 2.0.0-rc.0
Ionic CLI Version: 2.1.0
Ionic App Lib Version: 2.1.0-beta.1
ios-deploy version: 1.9.0 
ios-sim version: 5.0.8 
OS: Mac OS X El Capitan
Node Version: v6.4.0
Xcode version: Xcode 8.0 Build version 8A218a 

该提问来源于开源项目:ionic-team/ionic-cli

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答

20条回答

  • weixin_39874196 weixin_39874196 5月前

    Also got "Maximum call stack size exceeded", with live reload / browser refresh not working after that.

    点赞 评论 复制链接分享
  • weixin_39526741 weixin_39526741 5月前

    Any insights on this issue? Have you seen it occur before?

    点赞 评论 复制链接分享
  • weixin_39695672 weixin_39695672 5月前

    Same here.

    Your system information: Cordova CLI: 6.3.1 Ionic Framework Version: 2.0.0-rc.0 Ionic CLI Version: 2.1.0 Ionic App Lib Version: 2.1.0-beta.1 OS: Windows 7 Node Version: v6.6.0 Npm version:3.10.8

    
    JS changed:   XXX\www\build\main.js
    [14:42:18]  bundle dev update finished in 8.75 s
    [14:42:18]  sass started ...
    [14:42:18]  sass finished in 14 ms
    [14:46:23]  typescript compilation started ...
    [14:46:26]  bundle dev update started ...
    [14:46:29]  typescript compilation finished in 5.85 s
    [14:46:29]  bundle dev update started ...
    [14:46:29]  RangeError: Maximum call stack size exceeded
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:153:20)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
        at deepClone (XXX\node_modules\rollup\dist\rollup.js:165:18)
    
    [14:46:29]  sass started ...
    [14:46:29]  sass finished in 30 ms
    

    and also

    
    [14:28:50]  templateUpdate finished in 16.11 s
    FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
    
    点赞 评论 复制链接分享
  • weixin_39842029 weixin_39842029 5月前

    +1 Your system information: Cordova CLI: 6.1.1 Gulp version: CLI version 1.2.1 Gulp local: Local version 3.9.1 Ionic Framework Version: 2.0.0-rc.0 Ionic CLI Version: 2.1.0 Ionic App Lib Version: 2.1.0-beta.1 OS: Node Version: v4.6.0 Npm version:3.10.8

    点赞 评论 复制链接分享
  • weixin_39526741 weixin_39526741 5月前

    The call stack is happening within Rollup's deepClone method. Anyone have a public repo that is currently having this issue? It would help with troubleshooting.

    点赞 评论 复制链接分享
  • weixin_39526741 weixin_39526741 5月前

    I believe I found the issue. The watch process is spawning multiple rollup bundle processes rather than just managing the one. This would greatly increase the memory footprint. I am working on a fix now.

    Thanks for reporting this!

    点赞 评论 复制链接分享
  • weixin_39631953 weixin_39631953 5月前

    thanks a lot for looking into this!

    点赞 评论 复制链接分享
  • weixin_39926394 weixin_39926394 5月前

    https://github.com/driftyco/ionic-app-scripts/pull/44

    点赞 评论 复制链接分享
  • weixin_39962889 weixin_39962889 5月前

    Closed via https://github.com/driftyco/ionic-app-scripts/pull/44

    This should be fixed in the next release of app scripts.

    点赞 评论 复制链接分享
  • weixin_39631953 weixin_39631953 5月前

    Maximum call stack size exceeded error is gone but i am seeing the below error still that was occasionally thrown right after Max Stack before (see original issue description for another example).

    
    
     3172683 ms: Mark-sweep 1265.3 (1434.4) -> 1265.2 (1434.4) MB, 1549.5 / 0 ms [allocation failure] [GC in old space requested].
     3174187 ms: Mark-sweep 1265.2 (1434.4) -> 1265.0 (1434.4) MB, 1504.3 / 0 ms [allocation failure] [GC in old space requested].
     3175719 ms: Mark-sweep 1265.0 (1434.4) -> 1265.0 (1434.4) MB, 1532.1 / 0 ms [last resort gc].
     3177260 ms: Mark-sweep 1265.0 (1434.4) -> 1265.0 (1434.4) MB, 1541.1 / 0 ms [last resort gc].
    
    ==== JS stack trace =========================================
        2: arguments adaptor frame: 3->1
    Security context: 0x35d29d4c9e31 <js object>
        3: InnerArrayForEach(aka InnerArrayForEach) [native array.js:~946] [pc=0x37b82a7f57df] (this=0x35d29d404189 <undefined>,br=0x2b61d5897809 <js function>,bs=0x35d29d404189 <undefined>,w=0x9dd36daa579 <js array>,x=21)
        4: forEach [native array.js:~956] [pc=0x37b82b7954cc] (this=0x9dd36daa579 <js array>,br=0x2b6...
    FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
     1: 
    node::Abort() [/usr/local/Cellar/node/6.3.1/bin/node]
     2: 
    node::FatalException(v8::Isolate*, v8::Local<:value>, v8::Local<:message>) [/usr/local/Cellar/node/6.3.1/bin/node]
     3: 
    v8::Utils::ReportApiFailure(char const*, char const*) [/usr/local/Cellar/node/6.3.1/bin/node]
    
     4: 
    v8::internal::V8::FatalProcessOutOfMemory(char const*, bool)
     [/usr/local/Cellar/node/6.3.1/bin/node]
     5: 
    v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/usr/local/Cellar/node/6.3.1/bin/node]
    
     6: 
    v8::internal::LCodeGenBase::PopulateDeoptimizationData(v8::internal::Handle<:internal::code>)
     [/usr/local/Cellar/node/6.3.1/bin/node]
     7: 
    v8::internal::LChunk::Codegen()
     [/usr/local/Cellar/node/6.3.1/bin/node]
     8: 
    v8::internal::OptimizedCompileJob::GenerateCode()
     [/usr/local/Cellar/node/6.3.1/bin/node]
     9: 
    v8::internal::Compiler::GetConcurrentlyOptimizedCode(v8::internal::OptimizedCompileJob*)
     [/usr/local/Cellar/node/6.3.1/bin/node]
    10: 
    v8::internal::OptimizingCompileDispatcher::InstallOptimizedFunctions()
     [/usr/local/Cellar/node/6.3.1/bin/node]
    11: 
    v8::internal::Runtime_TryInstallOptimizedCode(int, v8::internal::Object**, v8::internal::Isolate*)
     [/usr/local/Cellar/node/6.3.1/bin/node]
    12: 0x37b82900961b
    
    </:internal::code></:message></:value></js></js></undefined></js></undefined></js>
    点赞 评论 复制链接分享
  • weixin_40007175 weixin_40007175 5月前

    I have exact same issue after 4-5 changes to the code. The templateUpdate started at around 9.8 secs, then it went up to 12, 13, 18, 40 and it broke.

    Lets hope that this issue will be resolved soon.

    Note: all packages are at its latest version

    点赞 评论 复制链接分享
  • weixin_39609071 weixin_39609071 5月前

    guys, is this related?

    
    08:14:07]  sass started ...
    [08:14:07]  sass finished in 16 ms
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:07]  bundle dev update started ...
    [08:14:08]  RangeError: Maximum call stack size exceeded
    
    
    
        [08:14:08]  RangeError: Maximum call stack size exceeded
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:163:2)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
        at deepClone (/Users/kabs/Dev/testapp/node_modules/rollup/dist/rollup.js:165:18)
    
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass started ...
    [08:14:08]  sass finished in 197 ms
    [08:14:08]  sass finished in 187 ms
    [08:14:08]  sass finished in 177 ms
    [08:14:08]  sass finished in 165 ms
    [08:14:08]  sass finished in 153 ms
    [08:14:08]  sass finished in 143 ms
    [08:14:08]  sass finished in 134 ms
    [08:14:08]  sass finished in 123 ms
    [08:14:08]  sass finished in 114 ms
    [08:14:08]  sass finished in 103 ms
    [08:14:08]  sass finished in 94 ms
    [08:14:08]  sass finished in 84 ms
    [08:14:08]  sass finished in 75 ms
    [08:14:08]  sass finished in 65 ms
    [08:14:08]  sass finished in 55 ms
    [08:14:08]  sass finished in 44 ms
    [08:14:08]  sass finished in 34 ms
    [08:14:08]  sass finished in 25 ms
    [08:14:08]  sass finished in 15 ms
    [08:14:13]  bundle dev update finished in 7.48 s
    [08:14:13]  sass started ...
    [08:14:13]  sass finished in 13 ms
    JS changed:   www/build/main.js
    
    点赞 评论 复制链接分享
  • weixin_39792747 weixin_39792747 5月前

    looks like it. Try not to save a file while the rebuild is in progress. Oh, and killall node is a quick way to clean up processes.

    点赞 评论 复制链接分享
  • weixin_39889481 weixin_39889481 5月前

    , try updating to the latest /app-scripts.

    
    npm install /app-scripts
    

    Thanks, Dan

    点赞 评论 复制链接分享
  • weixin_39927214 weixin_39927214 5月前

    I updated /app-scripts.0.30 and killall node but always the same error of

    点赞 评论 复制链接分享
  • weixin_39631953 weixin_39631953 5月前

    I am not getting any errors on 0.0.29

    点赞 评论 复制链接分享
  • weixin_39927214 weixin_39927214 5月前

    oups ^^" [17:26:57] ionic-app-scripts 0.0.23

    点赞 评论 复制链接分享
  • weixin_39834281 weixin_39834281 5月前

    Is this error fixed for anyone ..? Facing same problem here : https://stackoverflow.com/questions/44897670/error-in-ionic-cordova-build-android-prod

    点赞 评论 复制链接分享
  • weixin_39529128 weixin_39529128 5月前

    Same here. "Maximum call stack size exceeded" is happening too often together with "Allocation failed - process out of memory".

    And cli is noticeably slower now, before update build never didn't take more that 2.5 seconds now it is around 30 seconds.

    点赞 评论 复制链接分享
  • weixin_39631953 weixin_39631953 5月前

    Yeah, i noticed increased time too.

    点赞 评论 复制链接分享

相关推荐