Contents
Introduction
Installation
Guides
- Engine
- Profile
- Browser
- BrowserView
- Navigation
- Content
- Context menu
- DOM
- JavaScript
- Pop-ups
- Dialogs
- Downloads
- Chrome extensions
- Network
- Cache
- Cookies
- Proxy
- Authentication
- Permissions
- Plugins
- Printing
- Passwords
- User data profiles
- Credit cards
- Media
- Zoom
- Spell checker
- Deployment
- Chromium
Troubleshooting
Migration
Collecting crash dumps
DotNetBrowser runs Chromium in a separate native process. An error in the Chromium engine can lead to unexpected process termination. When this happens, Chromium generates a crash dump file with the debug information.
If Chromium process is unexpectedly terminated, and you received the Engine.Disposed event with non-zero exit code, submit a ticket and send us the generated crash dump file.
Where to find crash dump files
When one of the Chromium processes crashes, DotNetBrowser generates a crash dump file. The location of the dump file depends on the platform:
- Windows:
%appdata%\DotNetBrowser\dotnetbrowser.dmp.dir - Linux:
$HOME/.config/DotNetBrowser/dotnetbrowser.dmp.dir - macOS:
$HOME/.config/DotNetBrowser/dotnetbrowser.dmp.dir
To change the default directory, use the EngineOptions.CrashDumpDirectory property:
EngineOptions.CrashDumpDirectory = "C:\\DotNetBrowser\\crash-dumps";
EngineOptions.CrashDumpDirectory = "C:\DotNetBrowser\crash-dumps"