Introduction
Installation
Guides
- Engine
- Profile
- Browser
- BrowserView
- Navigation
- Content
- Context menu
- DOM
- JavaScript
- Pop-ups
- Dialogs
- Downloads
- Network
- Cache
- Cookies
- Proxy
- Authentication
- Permissions
- Plugins
- Printing
- Passwords
- User data profiles
- Credit cards
- Media
- Zoom
- Spell checker
- Deployment
- Chromium
Troubleshoot
- Logging
- Common exceptions
- Application does not terminate
- Video does not play
- Cannot sign in to Google acccount
- Color scheme
- Startup failure on Windows
- Slow startup on Windows
- Unresponsive .NET Application
- Unexpected Chromium process termination
- Unexpected behavior
Migration
Unexpected Chromium process termination
DotNetBrowser runs Chromium in a separate native process. An error in the Chromium engine can lead to unexpected process termination. The information about the native crash is stored in a crash dump file.
If Chromium process is unexpectedly terminated, and you received the Engine Crashed event, submit a ticket on the issue and share the generated crash dump file using an online file sharing service such as, for example, Dropbox, Google Drive, and others.
Collecting crash dumps
Windows
By default, crash dump file generation is enabled on Windows. In case of an unexpected Chromium process termination, DotNetBrowser generates a crash dump file and stores it in the %localappdata%\DotNetBrowser directory.
To change the default directory, use the EngineOptions.CrashDumpDirectory property. See the code sample below:
EngineOptions.CrashDumpDirectory = "C:\\DotNetBrowser\\crash-dumps";
EngineOptions.CrashDumpDirectory = "C:\DotNetBrowser\crash-dumps"