Port driver memory free

osxroolz@REDACTED osxroolz@REDACTED
Wed Mar 23 08:18:58 CET 2005

On Wed, 23 Mar 2005 11:15:40 +0600, "Casper" <casper2000a@REDACTED>
> More updates....
> Today when I checked the system, the Beam memory consumption was 253MB.

Most powerful tool in debugging is diffrential analysis.  Differential
analysis means you take version of the code with desirable properties
and version of program with ugly properties and step by step make them
more and more the same.  In this process you one day make one step which
turns good program into evil program and then that is the time when you
know exactly which step take you to hell.

Your case your having troubles with drivers.  You say

> Is there anyway to check the C port memory allocation?

the obvious answer is "turn your linking driver into own program which
communicates with Erlang through a socket".  Now unix tell you exactly
where memory being used.  Maybe you then have good version of your
program which let you think about which step is needed to make it evil
out of control memory eating beast.

But now your not using deferential analysis.  You are using ask mailing
list a lot of clueless questions type of analysis.


More information about the erlang-questions mailing list