Rank: Member
Groups: Member
Joined: 5/20/2015
Posts: 11
|
I am currently using the EO.WebBrowser 2015 version and I have a problem...
Sometimes the whole browser runs into a freeze for some reason.
There is probably some faulty logic somewhere within a javascript function.
but its kinda hard to debug as the problem only occurs maybe once a day.
I haven't been able to pinpoint exactly whats going wrong and would like to build in some logging.
right now it all freezes so dev-tools doesnt rly give me much(as it also freezes).
I'd like to write away some of the devtools info from the webBrowser to a file.
Any help on how to accomplish this?
Much appreciated.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, You can use console.log to write log message in JavaScript and then handle this event to capture the log messages on the .NET side: http://www.essentialobjects.com/doc/eo.webbrowser.webview.consolemessage.aspxYou can then write log file from that event handler. The "freeze" problem might also be a deadlock issue on our side. You can try to update to the latest build and see if that resolves the problem. If that still does not resolve the problem, you can start our Remote Debug Monitor tool when the error occurs and then notify us. We will be able to see some internal state of the browser engine through the Remote Debug Monitor. That may help us to find the root of the problem. See here for more information about this tool: http://www.essentialobjects.com/doc/common/remote_debug.aspxThanks!
|