Application does not terminate

When your application is running, you can notice several browsercore.exe or 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 IEngine and IBrowser instances you create, the more processes will be started. After the IBrowser or IEngine instance is disposed properly, the processes related to that instance will terminate automatically.

If an IBrowser or 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:

• Disposing Browser
• Engine Dispose

If the IEngine is disposed, all the IBrowser instances created by this IEngine will be disposed as well.