You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Testing] Re-enable macOS Memory Leak Device Tests for June 08 Candidate Branch #36614
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.
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
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.
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.
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
Activity
[-][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[/+]Ahamed-Ali commentedon Jul 16, 2026
This issue has been validated in Visual Studio Code 1.128.0 with Main and Inflight/candidate branch. It is reproducible on MacOS
kubaflo commentedon Aug 14, 2026
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.
kubaflo commentedon Aug 14, 2026
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 afixed-in-*label), and there was none.Sorry for the noise, and thanks to everyone who flagged it.
[-][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[/+][Mac Catalyst] Memory tests: Fix asynchronous and native lifetime cle…