Summary
As identified during the pre-release lifecycle and memory audit, several heavy components in workspace and grid result views retain references or lack explicit disposal calls:
DataGridStagingBuffer: Add explicit dispose() override to clear modified cells, inserted rows, and deleted row indices.- Workspaces (
PostgresSqlWorkspace, MysqlSqlWorkspace, SqliteSqlWorkspace, ExtensionTableView): Ensure any existing _stagingBuffer is explicitly disposed before creating a new one on query re-execution or page change, and cleanly disposed in the workspace dispose() lifecycle.
ResultsTab: Add dispose() override in _ResultsTabState to release memoized filtered rows and column caches upon unmounting.VirtualResultGrid: Reset _sortedRows, _columnWidths, and _columnOffsets in dispose() to immediately unbind large matrix references for faster garbage collection.
Summary
As identified during the pre-release lifecycle and memory audit, several heavy components in workspace and grid result views retain references or lack explicit disposal calls:
DataGridStagingBuffer: Add explicitdispose()override to clear modified cells, inserted rows, and deleted row indices.PostgresSqlWorkspace,MysqlSqlWorkspace,SqliteSqlWorkspace,ExtensionTableView): Ensure any existing_stagingBufferis explicitly disposed before creating a new one on query re-execution or page change, and cleanly disposed in the workspacedispose()lifecycle.ResultsTab: Adddispose()override in_ResultsTabStateto release memoized filtered rows and column caches upon unmounting.VirtualResultGrid: Reset_sortedRows,_columnWidths, and_columnOffsetsindispose()to immediately unbind large matrix references for faster garbage collection.