|
|
Rank: Newbie
Groups: Member
Joined: 6/8/2016
Posts: 4
|
We are using EO webbrowser in a DLL. Some other desktop application uses this DLL to load and show html pages. Sometimes EO.Base.Runtime.Exception occurs when we try to load the usercontrol (that shows html pages in an embedded webview). But this does not always happen.
I searched in the forums and saw that automatic crash reporting is enabled in EO products. Can you investigate crash reports and maybe find a clue about the reason of the error if possible? I can give you my license email for you to find the crash reports.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,172
|
Hi, Can you set your application ID so that we can match up the crash report on our side? See here for more details: https://www.essentialobjects.com/doc/common/crash_report.aspxNote that some crash can be resolved by us and some of them can not --- if the crash is in the Chromium browser engine, then we will usually wait for the chromium team to fix it since the chromium project is an extremely large projectwe thus it's beyond our capability to fix issues in the browser engine. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/21/2014
Posts: 129
|
Hi,
With the latest version of eo webbrowser, we've got the same EO Exception: System.Exception: Channel disconnected error happens sometimes (W7 computer only, it seems to happen in the WebView_CLosed event...)
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,172
|
Fabien wrote:Hi,
With the latest version of eo webbrowser, we've got the same EO Exception: System.Exception: Channel disconnected error happens sometimes (W7 computer only, it seems to happen in the WebView_CLosed event...) There are a lot of different scenarios that can cause this error. Some of them are in the browser engine, some of them are related to us. For the problems in the browser engine (this is the equivalent of Chrome browser's "Jim is dead" message), we usually will wait for the issue to be fixed in the chromium first. For other issues we will investigate. In order for us to look into it, we need it to be reproduced. Once it's reproduced, you can send a test project to us and we will investigate further. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/21/2014
Posts: 129
|
Hi,
Just to inform you that since versions after the 2016.1.75 our customers have frequently "Channel disconneted errors" (W7 & W10 now) No changes in our app except the upgrade of EO.WebRowser...
We've renew our licence and use the latest release available to download (16.2.93), but the problem remains.
The app crash randomly so, unfortunately we can't give you a scenario to reproduce this error.
We understand the difficulty to fix a bug that you can't reproducing but this situation is very prejudicial for us.
Thanks for your attention.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,172
|
Hi,
We can not identify any particular changes in 2016.1.75 that can cause this problem. We did not notice an increase on this error from other customers either. What you can do is to set your ApplicationID and we will continue monitor our automatic crash report database to see if we can spot anything there.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/21/2014
Posts: 129
|
Hi,
Our ApplicationID is 211_A26_AUSS
Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,172
|
Fabien wrote:Hi,
Our ApplicationID is 211_A26_AUSS
Thanks Hi, We only see a single crash report for this ID that seems to occurs when the application exits. By any chance that your crash report is turned off or is blocked? If the automatic crash report is blocked, you can also write code to manually save the crash report file and send it to us. See here for more details: https://www.essentialobjects.com/doc/common/crash_report.aspxThanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/21/2014
Posts: 129
|
Hi,
We've turned on the crash report only on a few computers since yesterday.
FYI, An user with the crash report enable just have the "Channel disconnected" error just 10-15 minutes ago.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,172
|
Hi,
We have received a number of crash reports from your application and they all points to similar locations when the WebView closes. We will continue investigating and if we find anything we will reply again. At this point we do not have any plan to release more updates build for the 2016 release. So this will most likely be addressed in the 2017 release.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/21/2014
Posts: 129
|
Hi,
Ok, so we hope that the 2017 release will be available soon and fix this bug because our customers are beginning to lose patience : /
Thanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/21/2014
Posts: 129
|
Hi,
We've upgraded to 17.0.40 and... "Channel disconnected" error still remains (only on 1 PC at the moment) :'(
The ApplicationID is always 211_A26_AUSS
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,172
|
Hi,
We are able to see the crash report when the window is destroyed, but we are not able to get much further than that. As you can understand, it's very hard for us to pin point the exact point of failure without being able to reproduce it. So if you have found anyway to reproduce it please let us know. In the mean time we will continue monitoring the crash report to see if we can figure out anything else.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/21/2014
Posts: 129
|
Hi,
Do you have find something on this crash ? The problem still remains on W7 and W10 PCs.
The ApplicationID is always 211_A26_AUSS
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,172
|
Hi,
We do not see any crash report with that ID for newer builds. The newest we can see is 17.1.14, which is still too old because we only keep a snapshot for everything (source code, debug symbols) for very recent builds. So make sure you update to the latest and notify us immediately after you see the crash. We can then check the report and see if we can find anything.
As always, if you can reproduce it, that will be the most effective way to track the issue down.
Thanks!
|
|