Closed simendsjo closed 3 years ago
This might be BenchmarkDotNet, and not Expecto. It seems the generated process just zombies out like
dotnet dab8e706-6f8d-47a7-bdb3-f67e9e956409.dll --benchmarkName Shadowcasting+ShadowcastBenchmark.ReferenceImplementation(Obstacles: 0.25, Size: 200, Radius: 1) --job InvocationCount=1, UnrollFactor=1 --benchmarkId 23
When benchmarking, expecto seems to freeze very often. So a benchmark with several parameters will never succeed. I can reduce it to a very small set, and change the parameters manually until all are handled.... Any good way to debug this?