- Context menu
- User data profiles
- Credit cards
- Spell checker
- 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
Application does not terminate
When your application is running, you can notice several
chromium.exe processes in Task Manager. These processes are always the child processes of your application’s process.
DotNetBrowser brings its own Chromium-based engine, and this engine uses these processes to do all the Chromium-related work. The more
IBrowser instances you create, the more processes will be started. After the
IEngine instance is disposed properly, the processes related to that instance will terminate automatically.
IEngine were not disposed properly, they will remain in memory and prevent your application from closing. The processes related to these instances will also remain running. These articles explain how to dispose these instances:
IEngine is disposed, all the
IBrowser instances created by this
IEngine will be disposed as well.