[Andrew John Sadler] Re: OutOfProcessEclipse still in the memory

attached mail follows:

Hi Vivek,

Could you send us a small example of your Java and ECLiPSe code that
exhibits this problem.  Also could you tell us which version of Java
you are using (e.g. Sun's JDK 1.4.1, or IBM's 1.3 etc...)

Since you have called the "destroy()" method on your
OutOfProcessEclipse objects, the ECLiPSe process should have
terminated and it should not have anything to do with garbage
collection.

If you could help by providing small examples I will investigate the
problem here.


Andrew Sadler

PS. Do these "mysterious" processes consume any CPU, or is it only memory?


Vivek Nigam <vivek.nigam@gmail.com> writes:

> Hello,
>
>               I am using the OutOfProcessEclipse, to run a prolog
> program through a JAVA interface.
>
>              There is a java server running continuosly and several
> clients can invoke a new OutOfProcessEclipse to run a query. At the
> end of the query I invoke the destroy method of OutOfProcessEclipse
> and it seems to work perferctly, because when I try to use the same
> engine again it returns the expected Exception :
> EclipseTerminatedException.
>
>              However, when I look at the processes that are running in
> my computer (btw I am using WinXP and Eclipse 5.8), the process is
> still there in the memory, so one client can generate several eclipse
> processes, and all of them stay in the memory until I shut the server
> down...
>
>               I was wondering if someone could help to figure out what
> is happening... or how can I kill the process from the memory, I
> suspect that this is a garbage collection problem... I am not sure...
>
>               Please let me know if you need more information.
>
> Many Thanks,
>
> Vivek Nigam