Rank: Advanced Member
Groups: Member
Joined: 7/20/2015
Posts: 52
|
Hello All,
Working with EO.WebBrowser 15.2.31.18. My application has 3 WebViews. I observed that often (but not always), my application's process still stays running even after I exit. In Process Explorer I noticed that the rundll32 procsses spawned by EO were still running under my application's process. So, I added a call to EO.Base.Runtime.Shutdown() inside an event handler for Application.Current.Exit. Unfortunately, this didn't resolve the issue. Even when stepping through in the debugger, I can see that the child rundll32 processes are still running after the EO.Base.Runtime.Shutdown() call. So for now, I have added code to forcibly kill these child processes using the System.Management and System.Diagnostics APIs.
Is there a better way? Did I miss something?
Thanks for your help!
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, This behavior is by design. EO.WebBrowser will start a number of child process. When your application exits, all the child processes will be closed except for one. One of them will stay in memory for a few seconds longer (about 5 seconds in the current build) and then it will exit --- regardless whether your application exits or Shutdown is called. We can probably add a flag for it to exit right away if you can give us a situation where this behavior would be problematic. Only one child process will stay longer --- so if you see more than one remain after your application closes, then that would be a bug. In that case please try to isolate the problem into a sample project and send the sample project to us and we will be happy to investigate further. See here for instructions on sending sample project: http://www.essentialobjects.com/forum/test_project.aspxThanks!
|