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

/home/explorer/lib/explorer.js:252 (RangeError: Maximum call stack size exceeded) #164

Closed
mdrankin opened this issue Mar 22, 2018 · 10 comments

Comments

@mdrankin
Copy link

Getting an issue now when attempting to sync. Have tried the solution given in issue #72 and issue #83 which is causing the issue as I get the same problem when attempting to sync right after forcing a delete of the index.pid file.

/home/explorer/lib/explorer.js:252 (RangeError: Maximum call stack size exceeded)
module.exports.syncLoop(array.length, function (loop) {
^

RangeError: Maximum call stack size exceeded
at /home/explorer/lib/explorer.js:252:52
at Object.next (/home/explorer/lib/explorer.js:189:18)
at /home/explorer/lib/explorer.js:260:14
at Object.next (/home/explorer/lib/explorer.js:189:18)
at /home/explorer/lib/explorer.js:260:14
at Object.next (/home/explorer/lib/explorer.js:189:18)
at /home/explorer/lib/explorer.js:260:14
at Object.next (/home/explorer/lib/explorer.js:189:18)
at /home/explorer/lib/explorer.js:260:14
at Object.next (/home/explorer/lib/explorer.js:189:18)
at /home/explorer/lib/explorer.js:260:14
at Object.next (/home/explorer/lib/explorer.js:189:18)
at /home/explorer/lib/explorer.js:260:14
at Object.next (/home/explorer/lib/explorer.js:189:18)
at /home/explorer/lib/explorer.js:260:14
at Object.next (/home/explorer/lib/explorer.js:189:18)

@avandurmen0001
Copy link

node --stack-size=20000 scripts/sync.js index reindex

@avandurmen0001
Copy link

run from explorer root folder

@mdrankin
Copy link
Author

Thanks, that seems to be running now. Will see how it goes.

@mdrankin
Copy link
Author

Note that I did drop the database and recreate it a couple of times previously and still encountered the issue. I guess if the index is stored elsewhere then it may work. It was falling over at block 344,381, and so far it's indexed 295,000 blocks

@mdrankin
Copy link
Author

My mongo username credentials keep dropping out so the sync stopped. Re-created the username and started it again. Would be better if Iquidus used a more reliable database engine.

@mdrankin
Copy link
Author

Thanks, looks like that has worked!

@mdrankin
Copy link
Author

After my Mongo credentials have stopped working for the 100th time, the re-syncing seems to be loading some transactions or blocks in our of order. They are certainly being displayed out of order. See below

image

@mdrankin
Copy link
Author

Here is another example
image

@avandurmen0001
Copy link

you need to reindex

@TheHolyRoger
Copy link
Collaborator

Reindex, it's massively improved in 8d44d4a

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

3 participants