question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Maximum call stack size exceeded

See original GitHub issue

Getting this error when trying to start the server:

Autostarting MongoDB instance...
Called MongoMemoryServer.start() method:
Called MongoMemoryServer.ensureInstance() method:
Starting MongoDB instance with following options: {
  "port":40609,
  "dbName":"testApp",
  "uri":"mongodb://127.0.0.1:40609/testApp",
  "storageEngine":"ephemeralForTest",
  "dbPath":"/tmp/mongo-mem-22YBfrGxMHBL73",
  "tmpDir":{
    "name":"/tmp/mongo-mem-22YBfrGxMHBL73"
  }
}
MongoBinary options: {
  "downloadDir":"/builds/goniyo/api/testApp/node_modules/.cache/mongodb-memory-server/mongodb-binaries",
  "platform":"linux",
  "arch":"x64",
  "version":"3.2.20"
}
Downloading:
RangeError: Maximum call stack size exceeded
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:1:1)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
    at WriteStream (/builds/goniyo/api/testApp/node_modules/graceful-fs/graceful-fs.js:201:29)
npm ERR! code ELIFECYCLE
npm ERR! errno 1

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:3
  • Comments:12 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
Negan1911commented, Oct 1, 2019

Seeing the same w/ last version, returning to 5.2.5 works 🤔

1reaction
MarceloPradocommented, Oct 9, 2019

Using 5.2.5 solved the issue for me.

Make sure your package.json is: "mongodb-memory-server": "5.2.5" instead of "mongodb-memory-server": "^5.2.5".

Read more comments on GitHub >

github_iconTop Results From Across the Web

javascript - Maximum call stack size exceeded error
It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you...
Read more >
JavaScript Error: Maximum Call Stack Size Exceeded
If you see the “Maximum Call Stack Size Exceeded” error, there's likely a problem with a recursive function within your JavaScript code. More ......
Read more >
Uncaught RangeError: Maximum call ... - Net-Informations.Com
This error is almost always means you have a problem with recursion in JavaScript code, as there isn't any other way in JavaScript...
Read more >
RangeError: Maximum call stack size exceeded - Educative.io
The most common source for this error is infinite recursion. You must have a recursive function in your code whose base case is...
Read more >
Maximum Call Stack Size Exceeded (Typescript Error) - Medium
Scenario for Maximum Call Stack Size Exceeded Error ... In your code, the possibility is, You are calling a function that is calling...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found