Assertion failed '(dstPos >= startPos) && (dstPos <= endPos)' during 'Optimize layout'

[jkotas]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=910444
Build error leg or test failing: System.Net.Security.Tests.WorkItemExecution
Pull request: #111086

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "(dstPos >= startPos) && (dstPos <= endPos)",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=910444
Error message validated: [(dstPos >= startPos) && (dstPos <= endPos)]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 1/8/2025 6:13:17 PM UTC

Report

Build	Definition	Test	Pull Request
914793	dotnet/runtime	System.Security.Cryptography.Tests.WorkItemExecution
910444	dotnet/runtime	System.Net.Security.Tests.WorkItemExecution	#111086

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	1	2

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[JulieLeeMSFT]

@amanasifkhalid, PTAL. It is blocking clean ci.

[amanasifkhalid]

Still struggling to get this to repro locally...

[amanasifkhalid]

I have a repro. There is a subtle bug in block layout where our 3-opt pass may determine a different start to the cold section than what our explicit cold code motion determined, if the cold section contains a call-finally pair where the first block is cold, but the second one isn't. Ensuring the behavior is consistent between these two sub-phases fixes this.