Currently we are manually hunting down memory leaks through Dev Tools. For some areas/components (e.g., notebook), this even needs to be done repeatedly. It would be helpful if we can capture the memory snapshots in CI and write some queries against the snapshot to analyze if there is any potential leaks.

A typical manual memory leak analysis for notebook

• Setup
  • Open OSS
  • Open notebook document A
  • Open notebook document B
  • Close both notebook documents
• Open Dev Tools, take a heap snapshot
  • Search NotebookTextModel object, there should be none
  • Search NotebookCellTextModel object, there should be none
  • Search NotebookEditor object, there should not be more than one (the editor group still holds a reference to the last editor)

cc @jrieken @connor4312 @Tyriar