Skip to content

[Testing] Re-enable macOS Memory Leak Device Tests for June 08 Candidate Branch #36614

Closed

Description

@HarishKumarSF4517

Description

The following mentioned Device Test cases have failed in Candidate branch due to this PR(#35487) appear to be regressions affecting device memory leak validation tests

After this #35487 PR introduced the test-related changes, the actual memory leak started occurring. Prior to these changes, no leak was observed. This needs to be fixed.

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

Failed Device Tests

Mac

  • MauiCALayerAutosizeToSuperLayerBehavior_DoesNotLeak

Steps to Reproduce

No response

Link to public reproduction project repository

No response

Version with bug

Unknown/Other

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

No response

Affected platforms

macOS

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

Activity

  1. changed the title [-][Testing] Re-enable Windows and macOS Memory Leak Device Tests on Candidate Branch[/-] [+][Testing] Re-enable Windows and macOS Memory Leak Device Tests for June 08 Candidate Branch[/+] on Jul 16, 2026
  2. Ahamed-Ali commented on Jul 16, 2026

    @Ahamed-Ali
    Contributor

    This issue has been validated in Visual Studio Code 1.128.0 with Main and Inflight/candidate branch. It is reproducible on MacOS

  3. added
    s/verifiedVerified / Reproducible Issue ready for Engineering Triage
    s/triagedIssue has been reviewed
    on Jul 16, 2026
  4. added this to the .NET 10 SR10 milestone on Jul 17, 2026
  5. kubaflo commented on Aug 14, 2026

    @kubaflo
    Contributor

    Closing as a duplicate of #36613. Same device-test re-enable failure and requested work; #36613 is the older canonical tracking issue. Please continue tracking and add any distinct evidence at #36613.

    Disclosure: this comment was generated by AI.

  6. kubaflo commented on Aug 14, 2026

    @kubaflo
    Contributor

    Reopening — this issue should not have been closed.

    It carries s/verified (a maintainer or partner reproduced it), s/triaged (it already went through triage), partner/syncfusion (a partner team is tracking it). Those labels mean the report was already confirmed as a real product defect, so it is not eligible for backlog cleanup closure. Closure here requires specific fix evidence (a merged PR that closes it, or a fixed-in-* label), and there was none.

    Sorry for the noise, and thanks to everyone who flagged it.

    Disclosure: this comment was generated by AI.

  7. changed the title [-][Testing] Re-enable Windows and macOS Memory Leak Device Tests for June 08 Candidate Branch[/-] [+][Testing] Re-enable macOS Memory Leak Device Tests for June 08 Candidate Branch[/+] on Sep 1, 2026
  8. added a commit that references this issue on Sep 4, 2026
    6193279
  9. locked and limited conversation to collaborators on Oct 7, 2026
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

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions