|
|
Rank: Advanced Member
Groups: Member
Joined: 7/17/2015
Posts: 51
|
Dear Support Team,
Since your update 20.0.53 we recognized a random crash in your browser engine. Suddenly the screen turns white and when we reload the site, we get the error message This WebView either has already been destroyed or is being destroyed.. It causes our whole software to stuck.
In the Runtime_CrashDataAvailable Event we get a crash log, but unfortunately the EO.Base.CrashDataEventArgs e.Message is empty.
We also get a WebviewException with the message RenderCrash.
It's very random, so I can't exactly tell you how to reproduce it.
I activated CrashLog. You should have some entries with the id 13a82b2e-4b28-4625-8b76-52971bb676da.
Do you know this issue or can you please tell me how to prevent from the complete crash.
Thank you in advance for some information.
Best regards!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
The crash report indicates that first the render becomes unresponsive and it prepares to raises RenderUnresponsive event. During that process it tries to collect the current JavaScript stack trace. This caused the crash. It appears that at certain points the stack trace can not be collected. If you can send us a test page we will try to debug into it and see if we can find out when the JavaScript stack trace can not be collected thus avoiding that step and proceed to RenderUnresponsive event directly.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 7/17/2015
Posts: 51
|
Hi,
Thanks for your reply. Unfortunately we cannot really send you a test application. The web application is hosted in our or our customers backend systems and this issue is very random.
Is there any way to recognize the crash, so that we can possibly react (restart or sth. like that). When the white screen appears the whole WPF application stucks. The WebViewException EventHandler seems not be fired.
Thanks!
Best regards!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
You can handle the WebView's Closed event and then check the event argument's Reason property to determine why it is closed. If the Reason is not "Normal", then you have a crash and you can try to recover.
Thanks!
|
|