Skip to content

[Testing] Re-enable Window Memory Leak Device Test for June 08 Candidate Branch #36613

New issue
New issue
Closed
#37310
Closed
[Testing] Re-enable Window Memory Leak Device Test for June 08 Candidate Branch#36613
#37310
Labels
area-controls-windowWindowpartner/syncfusionIssues / PR's with Syncfusion collaborationplatform/androidplatform/iosplatform/macosmacOS / Mac Catalystplatform/windowss/triagedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't working
Milestone
.NET 10 SR12

Description

@HarishKumarSF4517
HarishKumarSF4517
opened on Jul 16, 2026

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

Windows:

  • Window Does Not Leak

iOS:

  • Window Does Not Leak
  • Does Not Leak

Mac

  • Window Does Not Leak
  • Does Not Leak

Android

  • Does Not Leak
  • Window Does Not Leak

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

Windows, iOS, macOS, Android

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

Activity
  1. HarishKumarSF4517
    added 
    t/bugSomething isn't working
     on Jul 16, 2026
  2. dotnet-policy-service
    added 
    partner/syncfusionIssues / PR's with Syncfusion collaboration
     on Jul 16, 2026
  3. github-actions
    added 
    area-controls-windowWindow
     
    platform/android
     
    platform/ios
     
    platform/macosmacOS / Mac Catalyst
     
    platform/windows
     on Jul 16, 2026
  4. HarishKumarSF4517
    changed the title [-][Testing] Re-enable Window Memory Leak Device Test on Candidate Branch[/-] [+][Testing] Re-enable Window Memory Leak Device Test for June 08 Candidate Branch[/+] on Jul 16, 2026
  5. Ahamed-Ali commented on Jul 16, 2026 
    @Ahamed-Ali
    Ahamed-Ali
    on Jul 16, 2026
    Contributor
    This issue has been validated in Visual Studio Code 1.128.0 with Main and Inflight/candidate branch. It is reproducible on Android, iOS, MacOS and Windows
  6. Ahamed-Ali
    added 
    s/verifiedVerified / Reproducible Issue ready for Engineering Triage
     
    s/triagedIssue has been reviewed
     on Jul 16, 2026
  7. sheiksyedm
    added this to the  .NET 10 SR10 milestone on Jul 17, 2026
  8. kubaflo
    added a commit that references this issue on Aug 18, 2026
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    349dfc9
  9. github-actions
    modified the milestones:  .NET 10 SR10,  .NET 10 SR11 on Aug 18, 2026
  10. 13 remaining items
  11. kubaflo
    added 6 commits that reference this issue on Sep 27, 2026
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    d134adb
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    d26180d
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    5fda1f9
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    a754466
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    f650f17
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    a6ce4fb
  12. kubaflo commented on Oct 10, 2026 
    @kubaflo
    kubaflo
    on Oct 10, 2026
    Contributor
    Thank you for the report and the investigation details. We are closing this as completed: the named Window memory-leak device tests have been repaired and re-enabled, separating artificial async-state-machine roots from the Android adapter retention fix. This completes the test-repair task, not every memory-leak report.
    

    Supporting evidence: #37310 (merged into inflight/current).
    

    This records the merged source change; it does not imply that the fix is present in every released .NET MAUI package.
    

    If you can still reproduce the reported behavior in a build that includes the linked change, please comment here with the exact version and reproduction details so we can reopen and investigate. The existing reproduction and discussion remain available; a new issue is not required.
    

  13. kubaflo
    closed this as completedon Oct 10, 2026
  14. kubaflo
    added 6 commits that reference this issue on Oct 13, 2026
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    cf0193c
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    10b2863
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    e615c6e
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    58b72a5
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    1870a25
    Fix and Re-enable "Window Does Not Leak" and "Does Not Leak" Memory L…
    5a34966
  15. github-actions
    locked and limited conversation to collaborators on Nov 10, 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
    area-controls-windowWindowpartner/syncfusionIssues / PR's with Syncfusion collaborationplatform/androidplatform/iosplatform/macosmacOS / Mac Catalystplatform/windowss/triagedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't working
    Type
    No type
    Projects
    No projects
      Milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions