Skip to content

Assertion failed 'markedLastLoop && markedCurrLoop' #107518

Closed
Closed
Assertion failed 'markedLastLoop && markedCurrLoop'#107518
Assignees
kunalspathak
Labels
JitStressCLR JIT issues involving JIT internal stress modesarch-x86area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIblocking-clean-ci-optionalBlocking optional rolling runsos-windows
Milestone
10.0.0

Description

@BruceForstall
BruceForstall
opened on Sep 9, 2024

pipeline: runtime-coreclr jitstress-random
job: coreclr windows x86 Checked jitstress_random_1
test: managed/Compilation/Compilation/Compilation.cmd

set DOTNET_TieredCompilation=0
set DOTNET_JitStress=2be

C:\h\w\B8160A1E\p\watchdog.exe" 119 "C:\h\w\B8160A1E\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  Managed.dll 
19:49:13.347 Running test: managed/Compilation/Compilation/Compilation.cmd

Assert failure(PID 5788 [0x0000169c], Thread: 5524 [0x1594]): Assertion failed 'markedLastLoop && markedCurrLoop' in 'Microsoft.CodeAnalysis.CSharp.Symbols.SourceMemberContainerTypeSymbol:ForceComplete(Microsoft.CodeAnalysis.SourceLocation,System.Threading.CancellationToken):this' during 'Generate code' (IL size 877; hash 0xba50a687; FullOpts)

    File: D:\a\_work\1\s\src\coreclr\jit\emit.cpp:6067
    Image: C:\h\w\B8160A1E\p\corerun.exe

https://dev.azure.com/dnceng-public/public/_build/results?buildId=801287&view=ms.vss-test-web.build-test-results-tab

@dotnet/jit-contrib

Activity

  1. BruceForstall
    added
    JitStressCLR JIT issues involving JIT internal stress modes
    area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
    on Sep 9, 2024
  2. BruceForstall
    added this to the 9.0.0 milestone on Sep 9, 2024

  3. dotnet-policy-service commented on Sep 9, 2024

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Sep 9, 2024 – with Dotnet Policy Service
    Contributor

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

  4. JulieLeeMSFT
    assigned
    BruceForstall
    on Sep 9, 2024

  5. JulieLeeMSFT commented on Sep 9, 2024

    @JulieLeeMSFT
    JulieLeeMSFT
    on Sep 9, 2024
    Member

    @BruceForstall PTAL.

  6. JulieLeeMSFT
    added
    blocking-clean-ci-optionalBlocking optional rolling runs
    on Sep 9, 2024

  7. amanasifkhalid commented on Sep 9, 2024

    @amanasifkhalid
    amanasifkhalid
    on Sep 9, 2024
    Contributor

    @BruceForstall #107371 or #107403 might have exposed this

  8. BruceForstall
    added
    arch-x86
    os-windows
    on Sep 12, 2024
  9. amanasifkhalid
    assigned
    amanasifkhalid
    and
    BruceForstall
    and unassigned
    BruceForstall
    on Sep 13, 2024

  10. BruceForstall commented on Sep 13, 2024

    @BruceForstall
    BruceForstall
    on Sep 13, 2024
    ContributorAuthor

    @BruceForstall #107371 or #107403 might have exposed this

    I can repro the failure both before and after these PRs. (I tried 42f3dce, just before the first of those)

  11. BruceForstall commented on Sep 13, 2024

    @BruceForstall
    BruceForstall
    on Sep 13, 2024
    ContributorAuthor

    I verified this repros on .NET 9.

  12. amanasifkhalid commented on Sep 16, 2024

    @amanasifkhalid
    amanasifkhalid
    on Sep 16, 2024
    Contributor

    @BruceForstall I'm not able to repro this using a mainline build or the build from the failing CI run. I'm not sure if this is CPU-sensitive or not, but out of curiosity, what hardware did you repro this on?

  13. BruceForstall commented on Sep 16, 2024

    @BruceForstall
    BruceForstall
    on Sep 16, 2024
    ContributorAuthor

    @amanasifkhalid Here's my repro:

    set DOTNET_TieredCompilation=0
set DOTNET_JitStress=2be
set CORE_ROOT=c:\gh\runtime\artifacts\tests\coreclr\windows.x86.Checked\Tests\Core_Root
c:\gh\runtime\artifacts\tests\coreclr\windows.x86.Checked\Tests\Core_Root\corerun.exe C:\gh\runtime\artifacts\tests\coreclr\windows.x64.Checked\managed\Compilation\Compilation\Compilation.dll

    (I only build the tests for x64 Checked, but that shouldn't matter.)

    It does NOT fail if you use windows.x86.Debug. I'm testing on an Intel DevBox (AVX-512 capable).

  14. BruceForstall commented on Sep 16, 2024

    @BruceForstall
    BruceForstall
    on Sep 16, 2024
    ContributorAuthor

    This failure only exists with JitOptRepeat (which is enabled by the stress mode on this test). Setting set DOTNET_JitEnableOptRepeat=0 resolves the failure.

    Since OptRepeat is not enabled in .NET 9, this is a .NET 10 issue.

  15. BruceForstall
    modified the milestones: 9.0.0, 10.0.0 on Sep 16, 2024
  16. JulieLeeMSFT
    assigned
    jakobbotsch
    and
    kunalspathak
    and unassigned
    BruceForstall
    ,
    amanasifkhalid
    and
    jakobbotsch
    on Sep 30, 2024

  17. JulieLeeMSFT commented on Sep 30, 2024

    @JulieLeeMSFT
    JulieLeeMSFT
    on Sep 30, 2024
    Member

    @kunalspathak, it is related to loop alignment. PTAL.

  18. kunalspathak commented on Feb 6, 2025

    @kunalspathak
    kunalspathak
    on Feb 6, 2025
    Contributor

    Image

    even tried with OptRepeat explicitly and it passed. I don't remember this failing in last few months

    Image

  19. kunalspathak
    closed this as completedon Feb 6, 2025
  20. github-actions
    locked and limited conversation to collaborators on Mar 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

JitStressCLR JIT issues involving JIT internal stress modesarch-x86area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIblocking-clean-ci-optionalBlocking optional rolling runsos-windows

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions