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

channel disconnected [EOBrowser 20.2.34] Options
Eurice
Posted: Tuesday, September 8, 2020 6:27:29 AM
Rank: Advanced Member
Groups: Member

Joined: 12/10/2014
Posts: 126
Hello,

Since I updated to > 20 version I still face random channel disconnected.

I tryed many thing :
- different computer
- updating various driver (intel gpu for example)
- disabling gpu

But it's still happening and in a really random way, the webpage I invoke inside the browser are mostly the same as I was using on eo19.

I enabled the crash report on some computer; you can find those with "EURICE" id.

I know that chromium is a big project [...] and you might not be able to find anything without a reproductible case... but I could not find any way to reproduce it :(

Regards



eo_support
Posted: Tuesday, September 8, 2020 1:42:54 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,713
Hi,

Unfortunately we can't find anything. Most of the crash log do show a fairly consistent fashion. So they do seem to be caused by the same thing. For this kind of issues, usually we can only keep an eye on it and occasionally some other user may provide us some additional information which can lead to a solution/fix.

Thanks!
Fabien
Posted: Wednesday, December 2, 2020 4:49:42 AM
Rank: Advanced Member
Groups: Member

Joined: 7/21/2014
Posts: 118
Hi,

We are facing the same issue with the 20.2.63.0, the crash reporter is enabled with the application Id "211_A26_AUSS".

Some of our users report that the problem occurs on "big" web page using Vue.js may be the crash occurs with the javascript engine ?

Thanks
eo_support
Posted: Wednesday, December 2, 2020 5:30:31 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,713
Fabien wrote:
Hi,

We are facing the same issue with the 20.2.63.0, the crash reporter is enabled with the application Id "211_A26_AUSS".

Some of our users report that the problem occurs on "big" web page using Vue.js may be the crash occurs with the javascript engine ?

Thanks


Hi,

We have received many crash report from this application ID. It appears that most of them are caused by lacking of fallback font. Specifically, it fails on line 94 in this file:

https://chromium.googlesource.com/chromium/src/+/ef5cba111/third_party/WebKit/Source/platform/fonts/FontFallbackIterator.cpp

Obviously we have no way of knowing exactly what font it is looking for and why the system can not find a fallback font unless we have a repro project. We do know one case this can occur is if you use Windows Server Core 2019 Docker Container then it does not include any system font at all by default and it will trigger this error right away. However in that case it will fail consistently.

Thanks!
Fabien
Posted: Thursday, December 3, 2020 1:54:23 AM
Rank: Advanced Member
Groups: Member

Joined: 7/21/2014
Posts: 118
Hi,

Our users are running the app on Windows 10 (Pro Or Enterprise) so no Windows Server Core 2019.

Can we do something to catch this exception ? This error could crash the EO Engine ?

Thanks.
eo_support
Posted: Thursday, December 3, 2020 10:21:56 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,713
Hi,

There is no way you can catch and recover from this exception on the browser engine level. This is a check thrown by the browser engine in order to crash itself on purpose since it has exhausted all options.

You could however try to catch the browser engine crashes exception by handling WebView.Closed event and check the event argument's Reason property and check whether it is "Normal". If it is not "Normal", then it means the browser engine has crashed. You could then try to re-create your WebView and reload the same page (which will automatically restart the browser engine). This is similar to Google Chrome sometimes display an "He is dead, Jim!" message and asking you to reload the page. If you do this, you may need to handle EO.Base.Exception event to silent the "Channel disconnected" error.

The key here is browser engine crash does not equal to your application crash (since browser engine runs inside a separate process). So it might be possible for your application to recover from this to a certain degree.

Thanks!
Fabien
Posted: Wednesday, December 9, 2020 5:54:20 AM
Rank: Advanced Member
Groups: Member

Joined: 7/21/2014
Posts: 118
Hi,

Thanks for your reply. We are trying to check the e.Reason property to restart the webview when it crash. But when we recreate a WebView in th WebView_Closed event if the Engine is in the state "stopped" it still in this state an the new webview doesn't work.

The main problem here is the webview crash very often since we upgrade to the latest version (previously on 18.3.23 the crash is not present). Could you double check your log please to see if you can give us details on the reason of the crash or fix it in the engine.

For the font, the website only use Verdana wich is a standard font on Windows 10.

Thanks.

Eurice
Posted: Wednesday, December 9, 2020 6:12:29 AM
Rank: Advanced Member
Groups: Member

Joined: 12/10/2014
Posts: 126
Fabien wrote:
Hi,

Thanks for your reply. We are trying to check the e.Reason property to restart the webview when it crash. But when we recreate a WebView in th WebView_Closed event if the Engine is in the state "stopped" it still in this state an the new webview doesn't work.

The main problem here is the webview crash very often since we upgrade to the latest version (previously on 18.3.23 the crash is not present). Could you double check your log please to see if you can give us details on the reason of the crash or fix it in the engine.

For the font, the website only use Verdana wich is a standard font on Windows 10.

Thanks.



Hello,

I'm facing the exact same issue since september;

I had to create code that will recreate the engine when it crash and trigger the reload of every webviews when the new engine is ready.
It's not the best for user but still better than nothing.

Most of my users are using windows 10 and in most case load the same website (using the same font).

The crash happens randomly, I don't think it's due to a specific font.


Regards,
eo_support
Posted: Wednesday, December 9, 2020 10:50:37 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,713
Hi,

Without a test project there isn't much we can do ---- the Chromium project is extremely large and it can crash under numerous conditions. If you can isolate the problem into a test project that demonstrates the crash frequently, we will be able to debug it here and see what we can find. It is not practical for us to try to shoot in the dark and still hope to hit something meaningful.

Thanks!
Fabien
Posted: Wednesday, December 9, 2020 10:59:19 AM
Rank: Advanced Member
Groups: Member

Joined: 7/21/2014
Posts: 118
Hi,

I have no scenario to reproduce the crash..., like @Eurice say the crash happens randomly since we upgrade to v20+. Same website, same app but webengine crash randomly...

"It is not practical for us to try to shoot in the dark and still hope to hit something meaningful."
=> I've enabled the crash reporter so is not really a "shoot in the dark" ;)
Fabien
Posted: Wednesday, December 9, 2020 11:00:13 AM
Rank: Advanced Member
Groups: Member

Joined: 7/21/2014
Posts: 118
If the crash is linked to the chromium version used in v20 can you tell us when do you plan to upgrade chromium version ?
eo_support
Posted: Wednesday, December 9, 2020 11:06:38 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,713
Fabien wrote:
If the crash is linked to the chromium version used in v20 can you tell us when do you plan to upgrade chromium version ?


We are in the process of updating to Chromium 86 and it should be available in January. Crash report is not everything. It only provide us some pointers. Sometimes it can point to the problem right away, sometimes it is still miles away from the real root of the problem and in those cases a repro would help. That doesn't mean it has to reproduce consistently. For example, if we have something that can crash once every hour, then that could still be very helpful.
Fabien
Posted: Friday, January 15, 2021 6:28:26 AM
Rank: Advanced Member
Groups: Member

Joined: 7/21/2014
Posts: 118
Hi,

Do you have an estimate date of release for the version on the new Chromium version ?

Crash still happen and that's very frustrating for our users... We have no steps or samples to reproduce them it's seem to be totally random :(

The only thing we can tell is the crash not happening with EO.Webbrowser 19 version.

Thanks
eo_support
Posted: Friday, January 15, 2021 9:49:05 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,713
Hi,

Currently we are looking at mid February for our next release. However the same "crash if font is missing" logic still exists in the new Chromium engine. So I am not sure whether the new version will resolve this issue. :(

Thanks!
Fabien
Posted: Wednesday, January 20, 2021 3:04:32 AM
Rank: Advanced Member
Groups: Member

Joined: 7/21/2014
Posts: 118
Hi,

Thanks for the estimate date.

Do you believe this command line args https://peter.sh/experiments/chromium-command-line-switches/#disable-system-font-check could resolve the "font crash" ?

Thanks
eo_support
Posted: Thursday, January 21, 2021 6:21:46 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 22,713
Hi,

No. This flag is unrelated.

The issue is not really about font check --- the real issue is for some reason the browser engine can't get a fallback font. The check is just the quickest way to report this issue. Even if you were able to silence this check, you would still run into problems elsewhere as there is no font to use. So to resolve this issue we must find out exactly why there is no fallback font on the system and resolve that issue.

Thanks!
serializer
Posted: Thursday, January 28, 2021 8:37:18 AM
Rank: Advanced Member
Groups: Member

Joined: 5/9/2016
Posts: 78
We keep getting this as well. About 30 users have reported this so far. The resolution has been to right click on our application and choose "Run as administrator". Then it starts working. So some kind of permission error deep in the code.


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.