Welcome Guest Search | Active Topics | Sign In | Register

Essential Objects Product Support Forum » All Products » Support » Memory leak in EO.WebBrowsers underlying Rendering Engine

Memory leak in EO.WebBrowsers underlying Rendering Engine Options
Previous Topic · Next Topic
netvico GmbH
Posted: Thursday, October 30, 2014 5:48:55 AM
Rank: Newbie
Groups: Member

Joined: 10/24/2014
Posts: 3
Hello,

i noticed that in the EO.WebBrowser Control Chrome Version 33 is used.
Unfortunately this Version has an memory leak that causes an Crash of the EO.WebBrowser Processes. During this crash no exception is thrown - rundll process just exits an i see a white screen.
This is caused when setting the src of an Element.

Code to reproduce:
https://gist.github.com/daCuJo/8d1f77d9ad99cf190aef

How it looks like with EO.WebBrowser:


How it looks like in current chrome (38.0.2125.111)



As you can see, the Documents and Nodes are never released in the first image.

This is currently a big problem for us since we can not use the browser component with this bug.
I know that this bug does not depend on the EO.WebBrowser.

My Question is: Do you have plans to update the underlying engine? Or is there a possibility to use a specific dll for rendering (the current chrome). A Beta version with the current version or any solution would also work for us since this problem is a show stopper for us :/

Thanks in advance

See also:
https://code.google.com/p/chromium/issues/detail?id=359401
Back to top
 
eo_support
Posted: Thursday, October 30, 2014 11:05:43 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,196
Hi,

Thank you very much for the detailed information. As you can imaging, the best approach for this is to update to the newer version of Chrome and we do plan to re-sync with Chrome's code base as soon as possible. The current Chrome version is 38, so we are already a few versions behind so it is indeed due to an update and we are already planing to do this.

Having that said, updating Chrome engine is not as simple as replacing a DLL ---- we don't just load Chrome as a DLL, in fact we modify Chrome's source code extensively in order to integrate it with .NET seamlessly. Updating to a newer version of Chrome meaning getting the latest Chrome's source code and re-apply those changes. Even though we have rather sophisticated tools/process to do this (since we need to do it regularly), it's still a rather lengthy process and it needs extensively testing afterwards. So please bare with with while we are working on this.

Thanks!
Back to top
 


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.