CefSharp.MinimalExample/CefSharp.MinimalExample.OffScreen/crash_reporter.cfg

# Crash reporting is configured using an INI-style config file named
# "crash_reporter.cfg". This file must be placed next to
# the main application executable. 
# Comments start with a hash character and must be on their own line.
# See https://bitbucket.org/chromiumembedded/cef/wiki/CrashReporting.md
# for further details

[Config]
ProductName=CefSharp.MinimalExample.OffScreen
ProductVersion=1.0.0
AppName=CefSharp.MinimalExample
ExternalHandler=CefSharp.BrowserSubprocess.exe
Enable crash reporting by default - Set CopyToOutputDirectory in csproj files - It's important to make sure the crash_reporter.cfg is copied to the bin folder, it has to be next to your application exe. - Specify AppName in crash_reporter.cfg to have dumps generated to a folder in this case they will be generated at C:\Users\[CurrentUser]\AppData\Local\CefSharp.MinimalExample\User Data - If you are having trouble getting a dump, run your exe outside of Visual Studio, the debugger can sometimes interfere You can test crash reporting as outlined in https://bitbucket.org/chromiumembedded/cef/wiki/CrashReporting.md#markdown-header-testing Loading `chrome://crash` in the browser will crash the render process To confirm that crash reporting is enabled check the debug.log file, you should see a number of entries like Crash reporting enabled for process: browser 2019-11-15 06:13:59 +08:00			`# Crash reporting is configured using an INI-style config file named`
			`# "crash_reporter.cfg". This file must be placed next to`
			`# the main application executable.`
			`# Comments start with a hash character and must be on their own line.`
			`# See https://bitbucket.org/chromiumembedded/cef/wiki/CrashReporting.md`
			`# for further details`

			`[Config]`
			`ProductName=CefSharp.MinimalExample.OffScreen`
			`ProductVersion=1.0.0`
			`AppName=CefSharp.MinimalExample`
			`ExternalHandler=CefSharp.BrowserSubprocess.exe`