Skip to content

fix: memory leak in markers table - #333241

Merged
Ulugbek Abdullaev (ulugbekna) merged 1 commit into
microsoft:mainfrom
SimonSiefke:fix/memory-leak-markersTable
Sep 7, 2026
Merged

fix: memory leak in markers table#333241
Ulugbek Abdullaev (ulugbekna) merged 1 commit into
microsoft:mainfrom
SimonSiefke:fix/memory-leak-markersTable

Conversation

@SimonSiefke

Copy link
Copy Markdown
Contributor

Details

MarkersTable created its inner WorkbenchTable outside its disposable store. Switching Problems between table and tree views therefore retained the table's DOM listeners, sashes, scrollbars, and renderers.

Change

Register the inner table with MarkersTable so it is disposed together with its owner.

Before

When switching the Problems view between table and tree modes for 37 cycles, 217 named-function rows remain retained, including 2,479 DomListener instances:

before

After

No more markers table leak is detected. The matching 37-cycle result contains zero retained named-function rows.

Test Video

test-video.webm

Copilot AI balanced review requested due to automatic review settings August 28, 2026 19:58

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Registers the inner WorkbenchTable with MarkersTable so mode switches correctly dispose table-owned resources and prevent memory leaks.

Changes:

  • Adds WorkbenchTable to the owner’s disposable lifecycle.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ulugbekna
Ulugbek Abdullaev (ulugbekna) merged commit 6dddc81 into microsoft:main Sep 7, 2026
62 of 75 checks passed
@vs-code-engineering vs-code-engineering Bot added this to the 1.138.0 milestone Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants