Rank: Advanced Member
Groups: Member
Joined: 2/15/2014
Posts: 52
|
Hi Eo
Does EO Browser handle garbage collection? If I need the application to run 24x7 using EO.Browser, can it handle without memory issue?
I understand that javascript can cause memory leak which is beyond EO.browser's control, do you have any recommendation or suggestion on how to manage this still? Does destroying the WebView object and creating a new instance a good workaround?
Is there also a way to check the memory that EO.Browser is consuming so that the application can make an informed decision that it's
time to perform something, like recreating new WebView object or perhaps perform an application restart?
By the way, I will only need to create one WebView instance for my use-case.
Thanks
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
EO.WebBrowser is based on Google's Chromium browser engine. The browser engine is designed primarily for desktop application, not for server application. So run it for 24 by 7 would be pushing it.
Having that said, it does handle garbage collection whereever it can. For example, it has a garbage collector for the JavaScript engine. The .NET side has built-in garbage collection as well.
It does not provide any built memory usage measurement to you. Your best strategy should be probably passive --- recreate the WebView only when it crashes. This is what Chrome does. When a page crashes, it displays an error message stating the page has crashed and asking you whether you should recreate it. In your case, you can handle the WebView's Closed event and then recreate it automatically. Note that do not recreate the WebView inside Closed event handler. Use Dispatcher.Invoke or Control.BeginInvoke to delay it.
Hope this helps.
Thanks
|