Make thread executor a background thread. #570
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original implementation of XThread created a task on the standard TaskScheduler and did not spin up a parent thread. But instead the XThread container allowed "thread-like" operations to take place. The default TaskScheduler creates background threads by default.
When XThread was replaced with Thread it caused a real .NET thread to be created. This thread was created as a foreground thread which, when an application is terminated, will leave the application waiting on the termination of the thread.
This behavior is different than the original behavior with XThread.
Before, closing the application via Environment.Exit or letting it run to completion would kill all background threads. Now, the only way to terminate the executor thread is to call
ShutdownGracefullyAsync
. If the application using DotNetty was already callingShutdownGracefullyAsync
then the application would not experience any issues.DotNetty/src/DotNetty.Common/Concurrency/IEventExecutorGroup.cs
Line 29 in 47f5ec7
Foreground and background threads