Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while running scan #103

Closed
hackerabhinavverma opened this issue Mar 23, 2018 · 3 comments
Closed

Error while running scan #103

hackerabhinavverma opened this issue Mar 23, 2018 · 3 comments

Comments

@hackerabhinavverma
Copy link

I am getting below error while running for my aws account

/Users/abhinav/cplodsploit/scans/node_modules/aws-sdk/lib/request.js:31
            throw err;
            ^

RangeError: Maximum call stack size exceeded
    at /Users/abhinav/cplodsploit/scans/index.js:85:16
    at replenish (/Users/abhinav/cplodsploit/scans/node_modules/async/dist/async.js:836:21)
    at /Users/abhinav/cplodsploit/scans/node_modules/async/dist/async.js:842:29
    at /Users/abhinav/cplodsploit/scans/node_modules/async/dist/async.js:804:16
    at /Users/abhinav/cplodsploit/scans/index.js:112:13
    at /Users/abhinav/cplodsploit/scans/plugins/sns/topicPolicies.js:115:4
    at /Users/abhinav/cplodsploit/scans/node_modules/async/dist/async.js:365:16
    at replenish (/Users/abhinav/cplodsploit/scans/node_modules/async/dist/async.js:831:29)
    at /Users/abhinav/cplodsploit/scans/node_modules/async/dist/async.js:842:29
    at /Users/abhinav/cplodsploit/scans/node_modules/async/dist/async.js:804:16
@Dave3of5
Copy link

Are you running on windows by chance? I solved this by increasing the stack size:

node --stack_size=2000 index.js

This doubles the stack size and allows the process to complete. You may need to tweek that value to something different to get it to work on your system.

@rfletcher
Copy link
Contributor

rfletcher commented Apr 30, 2018

I hadn't seen this issue, but opened PR #111 after running into the same problem.

@matthewdfuller
Copy link
Contributor

Thanks for reporting @hackerabhinavverma - I've merged #111 which should fix this issue for you. Please let me know if you have any other trouble.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants