Skip to content
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

Revert "[threadpool-ms] Switch Monitor thread to a MonoThreadInfo (#3538)" #3550

Merged
merged 1 commit into from Sep 11, 2016
Merged

Revert "[threadpool-ms] Switch Monitor thread to a MonoThreadInfo (#3538)" #3550

merged 1 commit into from Sep 11, 2016

Conversation

alexrp
Copy link
Contributor

@alexrp alexrp commented Sep 11, 2016

There is a subtle problem with turning the monitor thread into a simple
MonoThreadInfo: It creates worker threads via mono_thread_create_internal (),
which allocates the thread object from the GC. No thread can allocate from
the GC unless it's actually attached, which the worker thread is not when
created with just mono_threads_create ().

)"

This reverts commit 2f88b8e.

There is a subtle problem with turning the monitor thread into a simple
MonoThreadInfo: It creates worker threads via mono_thread_create_internal (),
which allocates the thread object from the GC. No thread can allocate from
the GC unless it's actually attached, which the worker thread is not when
created with just mono_threads_create ().
@alexrp
Copy link
Contributor Author

alexrp commented Sep 11, 2016

cc @ludovic-henry

@alexrp alexrp merged commit 0a0be23 into mono:master Sep 11, 2016
@alexrp alexrp deleted the revert-tp-monitor branch November 29, 2017 00:10
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
Revert "[threadpool-ms] Switch Monitor thread to a MonoThreadInfo (mono/mono#3538)"

Commit migrated from mono/mono@0a0be23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants