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

Refactor more of thread creation into shared CoreLib partition #46244

Merged
merged 1 commit into from
Dec 24, 2020

Conversation

jkotas
Copy link
Member

@jkotas jkotas commented Dec 19, 2020

No description provided.

@Dotnet-GitSync-Bot
Copy link
Collaborator

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@jkotas
Copy link
Member Author

jkotas commented Dec 19, 2020

Follow up on #46181 (comment)

@vargaz
Copy link
Contributor

vargaz commented Dec 19, 2020

The mono changes look ok to me.

Copy link
Member

@kouvel kouvel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

@jkotas jkotas merged commit 833d353 into dotnet:master Dec 24, 2020
@jkotas jkotas deleted the thread-refactor branch December 24, 2020 08:01
jkotas added a commit to jkotas/runtime that referenced this pull request Dec 24, 2020
jkotas added a commit that referenced this pull request Dec 25, 2020
lambdageek added a commit to lambdageek/runtime that referenced this pull request Jan 13, 2021
monojenkins pushed a commit to monojenkins/mono that referenced this pull request Jan 13, 2021
Revert dotnet/runtime#46390 which reverted the Mono parts of dotnet/runtime#46244.

Fixes dotnet/runtime#46389

The issue was that the code in dotnet/runtime#46244 throws in `Thread` constructors before calling `Initialize`.  Which will then cause a finalizer to run on a partially-initialized thread object, which means that `ves_icall_System_Threading_InternalThread_Thread_free_internal` will be called with a null `MonoInternalThread:longlived` field.
jkotas pushed a commit that referenced this pull request Jan 13, 2021
* Revert "Partial rollback of #46244 to workaround #46389 (#46390)"

This reverts commit 43d0780.

* [threads] Check for null longlived thread data

This might happen on netcore if the managed Thread constructor throws an
exception before calling InitInternal.  In that case the finalizer may see a
partially initialized object.
akoeplinger pushed a commit to mono/mono that referenced this pull request Jan 13, 2021
Revert dotnet/runtime#46390 which reverted the Mono parts of dotnet/runtime#46244.

Fixes dotnet/runtime#46389

The issue was that the code in dotnet/runtime#46244 throws in `Thread` constructors before calling `Initialize`.  Which will then cause a finalizer to run on a partially-initialized thread object, which means that `ves_icall_System_Threading_InternalThread_Thread_free_internal` will be called with a null `MonoInternalThread:longlived` field.

Co-authored-by: lambdageek <lambdageek@users.noreply.github.com>
@ghost ghost locked as resolved and limited conversation to collaborators Jan 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants