You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using the stride engine just fine until today when suddenly even the most trivial stride templates (like the default ball) took 100% of all cores of my CPU. It led to massive freezing of my computer and the inability to do much of anything with stride. I am assuming something changed though what - I am not sure.
To Reproduce: Unfortunately I have no idea how to reproduce this... I cleaned and reinstalled everything to do with stride (.NET, MSBuild, VS etc.) but still didnt go away. I am assuming this must be a windows update?
Screenshots
I did some profiling to find where it was happening:
As you can see there is a massive portion of time being consumed on the wait call of LowLevelInfoSemaphore.Wait.
I downloaded and built my own latest version of stride - same problem
Temporary Fix
I bypassed Stride.Threading to System.Threading and it works normally again
Looks like it's stuck inside dotnet's LowLevelLifoSemaphore, can you share your dotnet --info with us, open a cmd, type dotnet --info and copy paste the result in a message.
Also your CPU just in case.
Release: 4.2.0.2293
Platform: Windows 11
I have been using the stride engine just fine until today when suddenly even the most trivial stride templates (like the default ball) took 100% of all cores of my CPU. It led to massive freezing of my computer and the inability to do much of anything with stride. I am assuming something changed though what - I am not sure.
To Reproduce: Unfortunately I have no idea how to reproduce this... I cleaned and reinstalled everything to do with stride (.NET, MSBuild, VS etc.) but still didnt go away. I am assuming this must be a windows update?
Screenshots
I did some profiling to find where it was happening:
As you can see there is a massive portion of time being consumed on the wait call of LowLevelInfoSemaphore.Wait.
I downloaded and built my own latest version of stride - same problem
Temporary Fix
I bypassed Stride.Threading to System.Threading and it works normally again
etc.
Let me know if you want me to dig further into this!
The text was updated successfully, but these errors were encountered: