Hi All,

I'm using the WPF WebControl which by default has a WebView property that is populated by a WebView object. Typically I start using that WebView by setting the Url and I'm on my merry way. :)

Under a certain scenario, users of my app can have a second window enabled when they launch the app, and this second window hosts the same web pages rendered in the WebViews of the first window. The requirement is that when they have this 2nd window turned on, we want to shut down the WebViews in the first window for reasons I won't get into here.

So i wrote some code to detect this 2-windows condition and call WebView.Close(true) on the WebViews in window #1. However, I found that the eowp.exe processes behind these WebViews stick around sometimes.

Was able to diff a WebView whose eowp got successfully terminated vs. one that didn't and found that the properties listed below were different. Here are the different properties of one that didn't get shut down:

CanEvalScript false bool
CanGoBack false bool
IsCreated false bool
StatusMessage null string
Title null string
Url "" string

My workaround was to tie into the StatusMessageChanged event and if the StatusMessage is not null I retry WebView.Close(true) and this seems to work. But I wanted to let the good people at EO know because this seems like a bug. WebView.Close(true) should always terminate the worker process I think.

Thanks!

JK