Does all processes shared one AppDomain in .netcore 3+ as mentioned in HERE ? What is the relationship of threadpool, process and appdomain in .netcore 3+ and how can I verify it ? Thanks!

Processes don’t share an appdomain, in .net core, each process supports one “appdomain”. In the old framework, an appdomain was an isolation tool. A process could host multiple appdomains and they could communicate with each other via marshaling. An appdomain could be unloaded. This was commonly used for plugin architecture. The plug-in could crash without hurting other host domains. Domains could load other domains. So they could be controlled with c# code. None of this support was added to .net core. Instead they have focused on loading and unloading assemblies similar to c/c++ In reality there is no real appdomain support in .net core. .net core is runtime hosted by an application.

AppDomain and ThreadPool

Accepted answer

Bruce (SqlWork.com) 56,686 Reputation points

2021-10-09T15:19:04.943+00:00

Processes don’t share an appdomain, in .net core, each process supports one “appdomain”.

In the old framework, an appdomain was an isolation tool. A process could host multiple appdomains and they could communicate with each other via marshaling. An appdomain could be unloaded. This was commonly used for plugin architecture. The plug-in could crash without hurting other host domains. Domains could load other domains. So they could be controlled with c# code.

None of this support was added to .net core. Instead they have focused on loading and unloading assemblies similar to c/c++

In reality there is no real appdomain support in .net core. .net core is runtime hosted by an application.
Please sign in to rate this answer.

1 person found this answer helpful.
forfcw 21 Reputation points

2021-10-11T03:14:38.933+00:00

Thanks for response.
I got a problem that System.Threading.Tasks.Task would not be executed when I start 3-4 processes and each process starting many threads. Obviously, the thread pool is consumed, but not by one process, but by all processes in .netcore.

Bruce (SqlWork.com) 56,686 Reputation points

2021-10-11T20:07:00.697+00:00

each process has its own thread pool as threads are owned by processes.

are you sure you know what a process is? how are you starting a process?

forfcw 21 Reputation points

2021-10-13T01:24:29.257+00:00

I couldn't help laughing
dotnet test.dll or just click the test.exe

Xingyu Zhao-MSFT 5,356 Reputation points

2021-10-14T02:17:53.51+00:00

Hi @forfcw ,

when I start 3-4 processes and each process starting many threads. Obviously, the thread pool is consumed, but not by one process, but by all processes in .netcore.

Could you provide more details of the sentence?
In order to help us reproduce the problem, you can consider sharing a sample here.

forfcw 21 Reputation points

2021-10-14T09:54:22.49+00:00

it's not easy to share a sample here. But after searching documents in MSDN, I just want to confirm something in .net core:

Different processes get different AppDomain.

Thread pools are completely isolated in different processes.

Here is the screenshot from MSDN with "For .NET Core, there is exactly one AppDomain."

Bruce (SqlWork.com) 56,686 Reputation points

2021-10-14T14:56:20.333+00:00

That is correct. In .net core a process can host one appdomain. Threads are owned by a process. Threads actually share the same process memory, but have individual stacks. A thread pool is just a collection of process threads used by the process to manage threads. A process can have multiple thread pools.

Other than using up O/S resources, the threads in one process have no effect on the threads in another.

You have not stated your actual issue, but thread limits are probably not it. Virtual Memory is the main limit. If you are using 32 bit windows you hit a limit at about 2000 threads a process due to stack allocation.
Sign in to comment

AppDomain and ThreadPool

0 additional answers