We have embedded Eo.WebBrowser into our application using the Multi-DLL build.
It works great overall, however on occasion in not entirely known circumstances the rundll processes that EO starts will be left open.

I've seen this come up regularly while testing in Visual Studio and terminating the process. I don't consider this an issue as I'm not working with the software in a normal manner at that point.

We also see this occur "in the wild" however. Sometimes it's accompanied by a crash with exceptions logged. we don't always have the full picture however.

I would like to try and clean up these processes when our application starts, but I want to be sure I'm not killing off any processes that were not created by my application. I wanted to know if there is any way I can uniquely identify these processes already.

If not would it be possible to add something to allow us to uniquely identify the processes?

I had initially tried to handle this by supplying a junk command line parameter containing a GUID. This worked overall, however it doesn't tag the primary EO process.

I'll investigate this, however I expect that it wont clean up processes that have been orphaned by a failed run of my application.