I've been running into some issues lately where I see the message:
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory
running a program (it's built on Node.js, but I'm interested in tracing
this on the v8 level).
>From all indications there's plenty of free memory, plenty of heap space
and the ulimit is not set too low, but we're still seeing this issue. Does
anyone have any suggestions on how to track down how we're triggering this
allocation failure?
Incidentally, while browsing through heap-inl.h there's a cryptic TODO...
fix this. comment.
540 if (__maybe_object__->IsOutOfMemory() ||
\
541 __maybe_object__->IsRetryAfterGC()) {
\
542 /* TODO(1181417): Fix this. */
\
543 v8::internal::V8::FatalProcessOutOfMemory("CALL_AND_RETRY_2",
true);\
544 }
\
Can someone shed light on where that comment came from, what the issue was
and what fixed it?
Thanks,
Brian
--
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
