GetResourceResponseFilter quits working in child windows after parent is closed.

[nchoate2]

I have a singleton class for IResourceRequestHandler. It overrides the GetResourceResponseFilter in our chromium browser. the overridden GetResourceResponseFilter is called appropriately for the main window and all popup windows, (child windows are created by window.open). However, if the main window is closed the interaction (back or navigate to new url) on the remaining child windows no longer cause the overridden GetResourceResponseFilter to be called. Any idea why? I can see my IResourceRequestHandler is still running, but it isn't being used so to speak.

[amaitland]

I can see my IResourceRequestHandler is still running, but it isn't being used so to speak.

What does still running mean exactly? Are any of it's other methods being called?

Could be a bug in CEF, try searching the issue tracker at https://github.com/chromiumembedded/cef

[nchoate2]

Still running means the IResourceRequestHandler is working and it's GetResourceResponseFilter gets called but just not for the child windows of the main window that was closed.

[nchoate2]

Looked in the issues for anything concerning getResourceResponseFilter, but nothing related to my issue. All of the issues were at least two years old.

[amaitland]

Still running means the IResourceRequestHandler is working and it's GetResourceResponseFilter gets called but just not for the child windows of the main window that was closed.

Are any of the other handlers firing for the child windows of the main window that was closed? You may need to restructure your code to make it easier to confirm this.

These classes weren't intended to be singletons

All of the issues were at least two years old.

Age is not really relevant, it's are any of them unresolved?

A very quick look at the CefSharp code and I think this is probably more likely a CEF issue, it should still have a reference to the CefClient instance for the main browser.

[amaitland]

To clarify are you closing the browser? Or are you actually Disposing of the ChromiumWebBrowser instance?

If you are using the default popup handling behavior then Disposing the ChromoiumWebBrowser instance would be freeing the references. So the behavior you are seeing would be expected if you call Dispose.

[nchoate2]

Yes, we are disposing the ChromiumWebBrowser. We will look to keeping the main browser window alive until all child windows are closed.