Hi,

The native browser engine runs inside eowp.exe, so this indicates a crash inside the browser engine. The browser engine is extremely large and complex, so numerous different scenario can cause it to crash. The most effective way to troubleshoot such crash is to reproduce it first. So if you have a way to reproduce the problem, please send a repro to us and we will debug into it and see what we can find. See here about more information on how to send repro to us:

https://www.essentialobjects.com/forum/test_project.aspx

If you can not reproduce it, you can try to collect crash log following these instructions:

https://www.essentialobjects.com/doc/common/crash_report.aspx

Make sure you are on the latest build before you try to collect the crash logs. Once we have the logs we will see what we can find.

Thanks!

Hi,

You should not try to covert our crash data. However way you convert/save it, you MUST covert it back to its original binary form if you want us to analyze it. So it doesn't matter how you encode it in your log as long as you have a way to decode it back.

Thanks!

Hi,

Unless you have explicitly set EO.Base.Runtime.EnableCrashReport to false, the crash report will be automatically sent to our server even if you did not handle CrashDataAvailable event. However in order for us to analyze these crash logs you will need to:

1. Provide some kind of information for us to locate your crash report. The recommended method is for you to explicitly set EO.Base.Runtime.ApplicationID to a unique value. If you did not set that in your code, you can let us know your application name and the end user's IP address and time of the crash (you may want to use private message to send us those information). We can then search our database to see if we can find matching crash logs;

2. You must be on a very recent build. Due to the enormous size and complexity of the Chromium browser engine, we only keep debug environment for very recent builds so we won't be able to analyze crash logs from older builds;

If that's not practical for you, you should consider creating a separate small test programs with the current build and handle CrashDataAvailable event in that test program, then coordinate with the end user to run the test program and collect the crash data. (We would be doing exactly the same thing if we had access to the end user's computer directly) You can also try to use these new APIs to collect diagnostic logs:

https://www.essentialobjects.com/doc/eo.base.diagnostictools.startdiagnosticlog.aspx

This will provide additional log information to us to troubleshoot the problem.

Thanks!