|
|
Rank: Advanced Member
Groups: Member
Joined: 7/17/2015
Posts: 50
|
Hi Support Team,
we have the issue that the webview crashes after some time. It happens once per shift (8 hours). Sometimes it happens more often. We checked the whole web application, but we cannot find the reason for this engine crash.
Everything seems to be fine. The processes in the task manager are also fine. Unfortunately we cannot provoke this engine crash. There are no big images, big data or a lot of traffic. Just simple controls. In Chrome the application works fine without any issues.
They use different versions of our application in the different production plants. So most devices are using your WebBrowser in Version 21.0.85 and some devices are using version 20.3.34. The webview crashes in both versions.
Do you have any idea about this crash? There should also be a CrashReport with the application IDs 6e5e72d6-c563-4326-af0a-9465efa6730b or 4ead3995-3082-463d-9699-3b8795ca6654.
Is it possible for you to find out the reason of the engine crash in the crash report.
Thanks in advance for some information!
Best regards!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/17/2015
Posts: 50
|
Hi,
in your change log I found the following fix in version 22.0.68: Fixed a handle and memory leak;
Does this fix the memory issue in the EO child processes?
If so, we would then update to version 22.0.68.
Best regards!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/17/2015
Posts: 50
|
Riephi wrote:Hi,
in your change log I found the following fix in version 22.0.68: Fixed a handle and memory leak;
Does this fix the memory issue in the EO child processes?
If so, we would then update to version 22.0.68.
Best regards! We tested 22.0.68 and it is also crashing.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,103
|
Hi, Please update to the current version and see if it helps. There are numerous different cases can cause crash, one common scenario is the JavaScript code uses too much memory causing the process to run out memory. This issue can usually be remedied by using the 64 bit build (the current build from our download page is 64 bit). If the problem continues with the current build, please try to capture the crash log. See here for more details: https://www.essentialobjects.com/doc/common/crash_report.htmlOnce we receive the crash log we will see what we can find. Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/17/2015
Posts: 50
|
Hi,
thanks for your quick reply! We will test the latest version.
But we already have enabled the crash report. Couldn't you find any entries with the given application IDs above?
Thanks!
|
|