WeiChiaChang/stacks-cli

Maximum call stack size exceeded

Opened this issue · 2 comments

Maximum call stack size exceeded

image

Error: Promise rejected with value: RangeError: Maximum call stack size exceeded
    at fs.depend (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:52313)
    at Ls.get [as newDepIds] (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:2663)
    at Ls.addDep (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:55459)
    at fs.depend (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:52337)
    at Ls.get [as newDepIds] (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:2663)
    at Ls.addDep (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:55459)
    at fs.depend (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:52337)
    at Ls.get [as newDepIds] (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:2663)
    at Ls.addDep (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:55459)
    at fs.depend (https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js:18:52337)
    at C:\Users\WMT_PS\AppData\Roaming\npm\node_modules\stacks-cli\node_modules\loud-rejection\index.js:27:12
    at Array.forEach (<anonymous>)
    at EventEmitter.<anonymous> (C:\Users\WMT_PS\AppData\Roaming\npm\node_modules\stacks-cli\node_modules\loud-rejection\index.js:23:24)
    at emitTwo (events.js:125:13)
    at EventEmitter.emit (events.js:213:7)
    at emit (C:\Users\WMT_PS\AppData\Roaming\npm\node_modules\stacks-cli\node_modules\signal-exit\index.js:77:11)
    at processEmit [as emit] (C:\Users\WMT_PS\AppData\Roaming\npm\node_modules\stacks-cli\node_modules\signal-exit\index.js:150:5)
    at process._fatalException (bootstrap_node.js:407:21)

Step to reproduce

Search stack for https://webmobtech.com

@kamerk22 wow... in fact I'm not pretty sure about the reason so far, but I will try to figure out in my spare time or weekends, big thanks for your time and issue report 👍

o3LL commented

I think Wappalyzer is trying to analyze this huge js file : https://webmobtech.com/public/vendor.4bbf67248dc6b9701422.js and just crash.