[ECOS] Memory leak in ecosynth in abnormal situation.

[John Carter <john dot carter at tait dot co dot nz>]

We have found a strong memory leak in ecosynth that occurs in an abnormal
situation.

If we run our application on the synthetic target with --io, ecosynth
starts up and behaves itself.

If we kill our application ecosynth doesn't exit.

When we rerun our application so there are now two copies of ecosynth
running simultaneously, ecosynth starts leaking memory at a ferocious
rate.

The obvious workaround is "Don't Do That", but it would be nice if
ecosynth was a bit more robust and could handle the situation gracefully.

Using gdb I can see the leak is somewhere in the .tcl part of ecosynth,
and probably not in the .c part. (A gdb stack trace it shows it running
the tcl interpreter.)

strace'ing it shows that it is repeatedly doing
select,gettimeofday,read,brk

Thank you,


John Carter                             Phone : (64)(3) 358 6639
Tait Electronics                        Fax   : (64)(3) 359 4632
PO Box 1645 Christchurch                Email : john.carter@tait.co.nz
New Zealand

A Million Monkeys can inflict worse things than just Shakespeare on
your system.

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss