-
Notifications
You must be signed in to change notification settings - Fork 12
Wait for submitted threads to end before terminating a command line procedure #446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Cherry pick to beta success |
iroqueta
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the WaitForThreadPoolEnd routine it seems that the SetMaxThreads method call that is outside the loop is unnecessary
You mean ThreadPool.GetMaxThreads right?. It is necessary to get the maxWorkerThreads value used inside the loop. |
…y the threads started by a Submit call type. It does not wait for other threads to finish (like the ones started by aspnet thread pool).
…rocedure - new implementation (#580) * Re-implement PR #446 with a new solution which takes into account only the threads started by a Submit call type. It does not wait for other threads to finish (like the ones started by aspnet thread pool). * Clear events after WaitAll ending. * Add log message to submit waiting routine. * Add unit test for submit function. Take into account limitation of WaitHandle.WaitAll and 64 threads.
Issue:24006