-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
System.Threading.Thread.StartCallback() - System.NullReferenceException #109697
Comments
The check at runtime/src/coreclr/vm/comsynchronizable.cpp Lines 227 to 231 in 7ee5b7d
_startHelper is non-null.
If you are getting into this method with |
Tagging subscribers to this area: @mangod9 |
Does this occur on ARM architecture by any chance? Maybe runtime/src/coreclr/System.Private.CoreLib/src/System/Threading/Thread.CoreCLR.cs Line 34 in 7ee5b7d
|
We don't currently have any servers running ARM |
Looking at the dump closer, I'm seeing exactly the same as ticket #103129. |
|
Yes, it looks exactly like #103129. I think the best way to get to the bottom of this is to find all places where GCHandles are set to point to |
Runtime: 8.0.10
OS: Ubuntu Server 22.04
We've had multiple Fatal exceptions in our production server causing docker containers to fail due to a
System.NullReferenceException
inSystem.Threading.Thread.StartCallback()
. Looking at the line in question/_/src/coreclr/System.Private.CoreLib/src/System/Threading/Thread.CoreCLR.cs @ 103
I can see the code is as follows:If
startHelper
is nullable, should the final line bestartHelper?.Run();
to prevent the null reference exception?The text was updated successfully, but these errors were encountered: