Maoni Stephens
Maoni Stephens
if I see this pattern - pinned handle -> object[] -> object I will just assume that those are _very likely_ static objects because static objects are always in an...
oops, sorry I didn't notice this. this repo is only for documentation purposes. for future references, please open an issue on our runtime repo. > we experienced out-of-memory events with...
could be https://github.com/dotnet/runtime/issues/82414 which I made a fix for in 8.0 (it has existed since forever). it does not affect running normally, only affects object validation which is only for...
do we want to do something about this? would blocking ci be a reason to backport?
these all have to do with running finalizers and we haven't made any changes there in a long time. these tests are flaky and of low value. I'd be fine...
I'm fine with disabling.
as a note, since we do not check the return value of calling `GCToOSInterface::BoostThreadPriority` it would be worthwhile making sure the priority is indeed changed :)
if the issue is fixed by setting noaffinitize to true, it usually indicates something else is preventing the GC threads from running. could you capture a ThreadTime trace with perfview...
thanks for the trace. so both GCs are induced. you can see this if you open the trace in perfview and look at the GCStats view GC Index | Pause...
that's a valid argument. you could even say that if you specified the GCHeapCount config, GC should just make the default of the GCNoAffinitize config true instead of false. I...