Port driver memory free

osxroolz@REDACTED osxroolz@REDACTED
Wed Mar 23 11:58:34 CET 2005

On Wed, 23 Mar 2005 13:28:53 +0600, "Casper" <casper2000a@REDACTED>

> if I have to change the Architecture to convert my Port driver to an
> external Port or Node, I loose the track of the memory leak point.

Your saying oposite of what makes sense.  When you divide into two
processes then you do not loose track but you have better track.  Three

One.  Memory leak goes away.  That was point of exorcise.  Now you know
the leaking it is in interface code.  Very short example with just
leaking code and nothing more possible now.  Maybe the mistake in how
you call interface.

Two.  beam continuse leaking.  P{roblem allmost certain in erlang code.

Three.  c process continuse leaking.  Problem is in C code.


More information about the erlang-questions mailing list