Anton Firszov

#### Report 2021/8/31: No new failure types, and no HTTP-level failures in 1.1/2.0 during the last week, although there are two occurrences of the 10060 (WSAETIMEDOUT) socket error despite firewall...

#### Report 2021/9/14: Checked both `main` and `release/6.0`. - No new failure types - All HTTP errors are gone - About 10% of the HTTP 1.1 Windows runs fails with...

#### Report 2022/8/1: - During the last week, all HTTP 1.1 and 2.0 Linux runs were successful on the CI - The Windows pipeline suffers from build failures, recently from...

#### SslStress 2022/8/3 Since #72940 there were 6 SslStress runs on Linux, all green. The Windows runs suffer from #73154.

Also be aware that the API shape of `System.Memory` went through significant changes. Eg. `IRetainable` does no longer exist, implementing reference counting is optional.

This seems to be definitely related to https://github.com/dotnet/runtime/issues/72365. @bjorg @kubalunacek @LarsAndreasEk or others, any chance you can produce & share a dump?

Actually, this could be caused by `ValueTask` misuse in user code see https://github.com/dotnet/runtime/issues/70486#issuecomment-1151175694.

I believe this is a low impact edge case. We won't be able to address it for 1.0.

I believe it would be better to address this in RC1.

@Sergio0694 or @emiliano84 can you please try if filling regions work? (`i.FillPolygon(Color.Red, new PointF[] { .... })` )