Flexsim instance is still running for over a minute

[Martin Saler]

During the development of external simulation components for Flexsim we encountered problems with the switching of processes from flexsimRTa.exe to flexsimRTb.exe. The main reason for our problems is that we allocated an external resource which can only be allocated once. We constantly get errors because one process blocks the resource. After taking a closer lock at it we encountered that the older Flexsim instance is still running for over a minute (or longer and with full memory usage). We solved this problem by simply killing the older process programmatically.

Therefore our question is: Can we safely kill the second, older Flexsim process after the new one compiled and started successfully? Or will we get nice, non-predictable side-effects from that?

Although we have not seen any side-effects yet, we fear that we could encounter some in production/stable environments…

Best wishes and thanks in advance,
Martin

[Anthony Johnson]

Honestly, I have no idea what might happen. My initial thought is that, since they are two separate processes, and really there isn't any communication between the processes (RTa just starts RTb and then kills itself), there shouldn't be any problem with explicitly killing RTa from RTb. But I really am not sure, so I guess if it appears to work, great!