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

FATAL ERROR: JS Allocation failed - process out of memory #122

Open
dnish opened this issue Mar 31, 2016 · 2 comments
Open

FATAL ERROR: JS Allocation failed - process out of memory #122

dnish opened this issue Mar 31, 2016 · 2 comments

Comments

@dnish
Copy link

dnish commented Mar 31, 2016

Hey,
any idead what's causing this error?

Kadira: Successfully connected
Kadira: completed instrumenting the app
FATAL ERROR: JS Allocation failed - process out of memory
Cluster: Exiting worker 3 with exitCode=null signalCode=SIGABRT
Cluster: Initializing worker 6 on port 9241
@MasterJames
Copy link

Do you get the same error running on a system/instance with more RAM?

@dnish
Copy link
Author

dnish commented Apr 2, 2016

Well, we have 32 GB RAM available and Kadira has shown me a use of 1 GB for our app :/. We have a system with 4 CPU cores.

We've now done some optimizations:

  • Reducing worker number from 4 to 2
  • Removed a slow publication which increased the CPU usage up to 60% and had a response time over 3 seconds (I think this was the main reason for the crashes)

Now everything seems to work fine, I'll test if the subscription was the problem and we are able to set the worker number again up to 4.

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

2 participants