Note: Advice in this article will only work for DotNetBrowser 1.
See the corresponding article for DotNetBrowser 2 here.

By default, when Chromium engine is crashed, DotNetBrowser generates DMP crash dump file and stores it in the %localappdata%\DotNetBrowser\dotnetbrowser.dmp.dir\ directory (e.g. c:\users\<username>\appdata\local\DotNetBrowser\dotnetbrowser.dmp.dir\chromium-main-2016-Jun-21-06-11-08.dmp). 


Since DotNetBrowser 1.13, you can explicitly configure the location that will be used for storing the dumps. The BrowserPreferences.CrashDumpDir is a read-write static property that you can use to specify the directory. This property should be specified before creating any Browser or BrowserView instance in your code.

If you would like to disable the creation of crash dump files, you need to set the "--crash-dump-dir" switch with an empty value: BrowserPreferences.SetChromiumSwitches("--crash-dump-dir=");


You can be notified about the Chromium engine crashes or unexpected termination by configuring the NativeCrashHandler for the Browser instance. The OnChromiumProcessExitNotOk method is called if the Chromium engine exit code indicates a possible error. This exit code can also provide additional information about the error: for example, -1073741819 (or C0000005) indicates a native access violation. 

When you see that Chromium engine is unexpectedly terminated or crashed, please go to the %localappdata%\DotNetBrowser\dotnetbrowser.dmp.dir\ directory and, if such file is present, share the file with us using an online file sharing service such as Dropbox, Google Drive, etc.

Getting crash dump file using Microsoft Debug Diagnostic Tool

For the previous versions of DotNetBrowser the crash dumps are not generated automatically. Therefore, you should use another approach to collect information about the crash.

To debug DotNetBrowser native binaries please use Microsoft Debug Diagnostic Tool to catch all exceptions in DotNetBrowser.Chromium.exe processes.

Here's instruction about how to configure this software to catch all native crashes/exceptions:

1. Download Microsoft Debug Diagnostic Tool (both 32- and 64-bit versions).

2. Install it in your target Windows environment. To install it just run MSI file.

3. Run your application and create at least one Browser instance.

4. Run Debug Diagnostic Tool and follow the instruction below:

4.1. Click Add Rule... button:

4.2. Select Rule Type - Crash and click Next:

4.3. Select A specific process and click Next

4.4. In the list of opened processes select/type DotNetBrowser.Chromium.exe and click Next

4.5. Click Next

4.6. Select directory where Tool will save Dump files (e.g. on your Desktop) and click Next:

4.7. Select Activate Rule Now and click Finish

Now you can work with your application and try to reproduce native crash in DotNetBrowser.Chromium.exe process. When native crash happens, this tool will generate DMP file in the directory you provided at 4.6 step.

When you reproduce native crash and get DMP file/files, please share them with us using an online file sharing service such as Dropbox, Google Drive, etc. and let us know. We will analyze DMP files, find out root cause of the native crash and fix it.