Rank: Advanced Member Groups: Member
Joined: 7/17/2015 Posts: 51
|
Hi Support Team,
some of our customers have the problem that our application is "freezing". But it is not the whole WPF application that freezes. It is only the content inside the WebView. After some time you are not able to interact with the application anymore. Touch is not working anymore and the CPU usage of the EO Worker Procceses are quite high with values over 50%-60%. It seems to run in a deadlock.
Here is some information about the device/ application: The customer is using NOAX Panel PCs running Windows 10 Enterprise LTSC version 1809. These devices have an integrated RFID reader to log in to the application by card. We listen for RFID events on COM port and then do a QueueScriptCall to pass the card id to the application. At some time the application seems to freeze and the JS calls aren't working anymore. You also cannot interact via touch. In our log files we saw that the values of the RFID reader are read, but the JS call does not work. The event will just fire after a few minutes or even after a few hours. CPU usage is quite high in your worker Processes. There are no crashes or errors. Input via mouse and keyboard works if you connect them. There is also an antivirus program called "Cylance Protect" running on the devices.
Unfortunately, you can't provoke this issue.
So we have some questions: - Do you know similar issues where touch doesn't work anymore at some time or that the CPU usage becomes quite high? - Or do you know any issue with such panel PCs or devices using this Windows version. - Do you have issues with antivirus programs like Cylance or maybe in combination with QueueScriptCall ? - Do you have any fix?
We use your WebBrowser in version 22.0.85.
Thanks in advance for some information!
Best regards!
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,217
|
Hi,
The most common reason for this to happen is when you have run away JavaScript code that never stops. For example, if your JavaScript code runs into an infinite loop, then you will run into this situation. If this is the case, then the only way to resovle such issue is to resolve the underlying faulty JavaScript code. As test, you can handle the WebView's RenderUnresponsive event. The above scenario would trigger this event. This can help you to confirm whether this is indeed what's happening.
Thanks!
|