I am forwarding this email to Yaws mailing list as well.
I am using R10B-8 and the yaws version is 1.48.
Was there any similar issue reported in old release?
---------- Forwarded message ----------
From: Stephen Han <kruegger@...>
Date: Thu, Sep 18, 2008 at 1:02 AM
Subject: Yaws shows high memory usage and erlang:port_info shows 'undefined'
To: - Erlang Questions <erlang-questions@...>
I am running yaws server and I am seeing the memory is increased to 500M
within a week.
If I do, erlang:memory() command
I do see binary is using up that much.
While try to debug this, I just ran the command [ erlang:port_info(X) || X
<- erlang:ports() ].
I do see almost 1100+ 'undefined' entries shows up. Is this normal?
Is there any relation with number of 'undefined' erlang ports and memory
Can anyone point where the possible issues lie?
thanks in advance...
Stephen Han wrote:
> I do see binary is using up that much.
> While try to debug this, I just ran the command [ erlang:port_info(X) ||
> X <- erlang:ports() ].
> I do see almost 1100+ 'undefined' entries shows up. Is this normal?
No, not that I know of. Yaws opens a lot of ports though, each
file:open(F, [raw]) becomes one port.
You need to debug this more - it can be anything. You need to
use process_info(P, memory) to figure out which process are using
the memory. Once you know that, you can do
process_info(P, stack_trace) on them to see where they are in the code.