It was more just for bringing it to your attn. I often try crazy stuff that MoI tries to calculate and sometimes if you get 10 minutes into a calculation and want to cancel, you may just have to wait another 10 for MoI to cleanup (or not), so I just force the issue.

I can see someone building up a few of those so I was just wondering. harmless.

Also for my own knowledge if there was some reason that garbage cleanup couldnt be done between the to procs when killed.

Just trying to do some beta with you instead of just using you as my modeling teacher! :O

Burr

Hi Burr,

> Also for my own knowledge if there was some reason that
> garbage cleanup couldnt be done between the to procs
> when killed.

Well, the tricky part with that kind of termination is that the regular cleanup stuff done at normal program exit by moi.exe is not done, because that moi.exe process just gets stopped in its tracks and nuked.

So the cleanup logic for handling that actually has to go in the moi_commandprocessor.exe process instead.

- Michael

Hi Burr, I've tuned this up for the next release to behave better.

Now if you terminate moi.exe with the Windows Task Manager, any associated command processor .exes that are associated with it will also get cleaned up after a possible short delay of up to 3 seconds.

Thanks for reporting it!

- Michael