Skip to content

Mono Browser wasm Release failures on runtime rolling build #69850

Closed
#69863
Closed
Mono Browser wasm Release failures on runtime rolling build#69850
#69863
Labels
arch-wasmWebAssembly architecturearea-ExceptionHandling-coreclronly use for closed issues

Description

@mkhamoyan
mkhamoyan
opened on May 26, 2022

Description

Last rolling build of runtime fails with following exceptions

Unhandled Exception:
StackOverflowException
[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException: The requested operation caused a stack overflow.
at ExplicitTailCallNoSO.CalculateSumWithTailCall(Int32 n, Int32 sum

or

Unhandled Exception:
StackOverflowException
[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException: The requested operation caused a stack overflow.
at Class1.Recurse4(Int32 depth, Object o1, Object o2)
for more info please look https://dev.azure.com/dnceng/public/_build/results?buildId=1790753&view=ms.vss-test-web.build-test-results-tab

Reproduction Steps

Check last rolling build of runtime https://runfo.azurewebsites.net/view/build/?number=1790753

Expected behavior

Tests should pass

Actual behavior

[ERROR] FATAL UNHANDLED EXCEPTION: System.StackOverflowException

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on May 26, 2022
  2. ghost removed
    untriagedNew issue has not been triaged by the area owner
    on May 26, 2022
  3. ghost added
    area-ExceptionHandling-coreclronly use for closed issues
    on May 26, 2022

  4. mkhamoyan commented on May 26, 2022

    @mkhamoyan
    mkhamoyan
    on May 26, 2022
    ContributorAuthor

    From commits seems it can be related this PR , @radical could you please check? can it be related?

  5. radical commented on May 26, 2022

    @radical
    radical
    on May 26, 2022
    Member

    This was failing before that PR too - #69517

  6. radical commented on May 26, 2022

    @radical
    radical
    on May 26, 2022
    Member

    And the other failure is #43200

  7. mkhamoyan commented on May 26, 2022

    @mkhamoyan
    mkhamoyan
    on May 26, 2022
    ContributorAuthor

    I see , in rolling build it was hit first time in last 2 weeks. So we will disable tests?

  8. radical commented on May 26, 2022

    @radical
    radical
    on May 26, 2022
    Member

    Yeah, I can disable JIT/Directed/tailcall/tailcall/tailcall.sh. Based on #43200 (comment), I think we don't need to disable JIT/Performance/CodeQuality/Linq/Linq/Linq.sh.

  9. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on May 26, 2022
  10. radical
    added
    arch-wasmWebAssembly architecture
    on May 26, 2022
  12. radical
    closed this as completedin #69863on May 27, 2022
  13. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on May 27, 2022
  14. ghost locked as resolved and limited conversation to collaborators on Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    arch-wasmWebAssembly architecturearea-ExceptionHandling-coreclronly use for closed issues

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions