Crashing process on FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
1,242 views
Skip to first unread message
Vivek Goel
Oct 26, 2013, 9:44:47 AM10/26/13
to nod...@googlegroups.com
Hi,
I have faced one issue, In stderr there was one log having message
"FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory"
But process didn't crashed. It was running. If it was fatal error , it should have been crashed right ?
If yes, what could be the cause that it didn't crashed.
If No,
I have faced one issue, In stderr there was one log having message
"FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory"
But process didn't crashed. It was running. If it was fatal error , it should have been crashed right ?
If yes, what could be the cause that it didn't crashed.
If No,
- Will my process in responding state in such cases ?
- How can I make it crash on such fatal error.
Fedor Indutny
Oct 26, 2013, 10:15:59 AM10/26/13
to nod...@googlegroups.com
Hi!
Could it be that it was dumping a core file, and thus hanging (because there was a lot of memory to dump)? What's your `ulimit -c`?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Vivek Goel
Oct 26, 2013, 1:38:10 PM10/26/13
to nod...@googlegroups.com
I have ulimit set at unlimited.
regards
Vivek Goel
You received this message because you are subscribed to a topic in the Google Groups "nodejs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nodejs/v8JBMEsN8yA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nodejs+un...@googlegroups.com.
Fedor Indutny
Oct 26, 2013, 2:59:02 PM10/26/13
to nod...@googlegroups.com
That basically means, that core dumps are enabled and the process isn't crashing, because OS is dumping data to disk.
You should try setting it to 0, or waiting for dump to end.
Vivek Goel
Oct 27, 2013, 6:16:47 AM10/27/13
to nod...@googlegroups.com
It was not problem related to coredump. Process was in that state for more than 30 minute.
I am using some third party modules which used node domain. Any chances that it caught in node domain and lost there ?
regards
Vivek Goel
Fedor Indutny
Oct 27, 2013, 6:29:57 AM10/27/13
to nod...@googlegroups.com
That's very unlikely. Is it using a lot of CPU, or just hanging around?
Reply all
Reply to author
Forward
0 new messages