Logo
My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

Webbrowser suddenly being disposed? Options
M.Kramer
Posted: Tuesday, July 23, 2019 9:17:36 AM
Rank: Advanced Member
Groups: Member

Joined: 11/3/2015
Posts: 51
Ah, okay sorry...

I'll change it in my program.

fyi I found a memory leak in the Webside.
"Normal chrome" has no problem with it, but EO. ... But I could fix it.

Now I'm going to monitor, if there are other problems, that causses crashes, too.
eo_support
Posted: Tuesday, July 23, 2019 3:28:12 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,568
M.Kramer wrote:
Ah, okay sorry...

I'll change it in my program.

fyi I found a memory leak in the Webside.
"Normal chrome" has no problem with it, but EO. ... But I could fix it.

Now I'm going to monitor, if there are other problems, that causses crashes, too.


It's not uncommon that a page runs with "Normal Chrome" but not with EO because of memory leaks. EO child processes run in 32 bit mode and Google Chrome usually runs in 64 bit mode. So if there is a memory leak, Google Chrome usually can tolerate it longer. However in any case a memory leak in your page should always be fixed.
M.Kramer
Posted: Wednesday, July 24, 2019 1:16:13 AM
Rank: Advanced Member
Groups: Member

Joined: 11/3/2015
Posts: 51
Quote:
However in any case a memory leak in your page should always be fixed.


of course ;)
M.Kramer
Posted: Wednesday, July 24, 2019 2:02:34 AM
Rank: Advanced Member
Groups: Member

Joined: 11/3/2015
Posts: 51
Hi,

next case (as I told you, I think there are more than one problem)
The Webengine crashes sometimes at one user while she is opening the ContextMenu.

Sadly no crash report except System.Exception: This WebView either has already been destroyed or is being destroyed.


Quote:

tmpWebView.BeforeContextMenu += new BeforeContextMenuHandler(WebView_BeforeContextMenu);


void WebView_BeforeContextMenu(object sender, BeforeContextMenuEventArgs e)
{
e.Menu.Items.Clear();
e.Menu.Items.Add(new EO.WebBrowser.MenuItem("Ausschneiden", CommandIds.Cut));
e.Menu.Items.Add(new EO.WebBrowser.MenuItem("Kopieren", CommandIds.Copy));
e.Menu.Items.Add(new EO.WebBrowser.MenuItem("Einfügen", CommandIds.Paste));
e.Menu.Items.Add(new EO.WebBrowser.MenuItem("Löschen", CommandIds.Delete));
e.Menu.Items.Add(EO.WebBrowser.MenuItem.CreateSeparator());
e.Menu.Items.Add(new EO.WebBrowser.MenuItem("Drucken", CommandIds.Print));
}
eo_support
Posted: Wednesday, July 24, 2019 11:46:11 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,568
M.Kramer wrote:
Hi,

next case (as I told you, I think there are more than one problem)
The Webengine crashes sometimes at one user while she is opening the ContextMenu.

Sadly no crash report except System.Exception: This WebView either has already been destroyed or is being destroyed.


Please try to reproduce it first. There isn't much we can do at all if you just say it crashed.
M.Kramer
Posted: Wednesday, July 31, 2019 5:33:10 AM
Rank: Advanced Member
Groups: Member

Joined: 11/3/2015
Posts: 51
Hi,
now I'm abel to reproduce it.
It appears after several (20-30?) clicks on the right mous button.

I've got e crashreport in .dat format and will send it to you now.

eo_support
Posted: Wednesday, July 31, 2019 2:10:53 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,568
Hi,

Please try to isolate the problem into a test project and send the test project to us. This crash seems to have occurred after the WebView has already been closed. So it is not the root of the problem. The root of the problem is somehow the WebView is closed and we have to find out why it has been closed.

Thanks!
PS
Posted: Wednesday, September 4, 2019 6:01:26 AM
Rank: Advanced Member
Groups: Member

Joined: 10/24/2018
Posts: 88
Hello, a new comment on my initial issue here, it appears that no crashdata is collected/saved for the issue that we are experiencing.
How do we continue to debug it?

So far it looks like an important factor is that lots of Javascript is being executed on the page after certain user interactions, these are all queued via QueueScriptCall.

Please give us some direction on what we can do next to get to the root of this issue because in this way we cannot release our product with the EO browser to all of our customers and we'll be forced to stop using the EO browser eventually, which would be a shame because it is better in most regards than the standard WinForms control.

Is there maybe in your code something that can dispose/destroy the browser control if something goes wrong when executing Javascript?
eo_support
Posted: Thursday, September 5, 2019 9:23:01 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 21,568
Hi,

There isn't much we can do unless you can reproduce it. Chromium has over 20 million lines of code and it is not possible for us to "guess" what could be wrong in these 20 million+ lines of code. The only way to precisely resolve an issue is to reproduce it, debug it, fix it and then verify it. Any other way would be just shooting in the dark. We would either miss the problem completely, or accidently hit a switch that turns of the alarm but not fixing the issue itself. Not only we would be wasting our time in that case, the same problem could surface for you again later at a different place in a different form. So it has no benefit to you either. As such for this kind of issue it must be reproduced first.

Thanks!


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.