Object reference not set to an instance of an object at System.Threading.ThreadInt64PersistentCounter.get_Count() #71583
Comments
ghost
added
the
|
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
|
Tagging subscribers to this area: @mangod9 Issue DetailsDescriptionI am running an AspNet Core project with a Worker running as a background service. Very rare and random I got this exception:
Stacktrace: Reproduction StepsThis happened very randomly, I don't know how to reproduce. Just have an aspnet core app with a Worker as a background service. I let it run for several hours in VS 2022 debugger. Expected behaviorShould not throw an exception. Actual behaviorThrows a null reference exception. Regression?No response Known WorkaroundsNo response Configuration.NET 7.0 Preview 5. Other informationNo response
|
|
It's not clear to me how this could be happening from the code. Try enabling just-in-time debugging in VS and if possible share a crash dump if it happens again. |
|
I did enable my just in time debugging. Next time it happens I will provide more information. It didn't happen since then. Please keep this issue open in case someone encounter the same issue. |
Description
I am running an AspNet Core project with a Worker running as a background service.
Very rare and random I got this exception:
Object reference not set to an instance of an object.Stacktrace:
...at System.Threading.ThreadInt64PersistentCounter.get_Count()Reproduction Steps
This happened very randomly, I don't know how to reproduce. Just have an aspnet core app with a Worker as a background service. I let it run for several hours in VS 2022 debugger.
Expected behavior
Should not throw an exception.
Actual behavior
Throws a null reference exception.
Regression?
No response
Known Workarounds
No response
Configuration
.NET 7.0 Preview 5.
Windows 11 Insider Build 25151.
Intel Core i3 x64 (NUC 8).
64 GB of RAM.
2TB Samsung NVMe Pro 980 of Disk Space.
Other information
No response
The text was updated successfully, but these errors were encountered: