Skip to content

Test popular extensions with Electron 22 and custom memory allocator #177646

@bpasero

Description

@bpasero

Refs: #177338

Complexity: 5

Create Issue


The new custom memory allocator in VS Code with Electron 22 should be tested to ensure:

  • our top extensions continue to work as before
  • extensions with known problematic native modules continue to work as before and do not crash VS Code

Prerequisites

Testing has to be done on (orange) VS Code exploration builds with Electron 22. Downloads:

Test Strategy

  • do exploratory smoke testing of the extension triggering some of its functionality to verify it works
  • see the native module the extension depends on to try to explicitly trigger the native code if possible
  • limit testing to 5 minutes max, since there are many extensions to test
  • watch out for extension host crashes or crashes in general

Test Top Extensions

With the exception of ms-toolsai.jupyter, none of the extensions below have known native modules that break the V8 memory cage, but nevertheless they are popular extensions we want to ensure work properly.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions