-
Notifications
You must be signed in to change notification settings - Fork 37.6k
Closed
Description
Refs: #177338
- macOS: @isidorn
- linux: @deepak1556
- windows: @bpasero
Complexity: 5
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.
- ms-toolsai.jupyter
- MS-vsliveshare.vsliveshare
- WallabyJs.quokka-vscode
- vsciot-vscode.vscode-arduino
liximomo.sftpIsidor: this extension is deprecated I suggest to not test it.- negokaz.live-server-preview
- Blackboxapp.blackbox isidor: it requires an account so I just tested functionality that does not require acc
- ban.spellright
- Lokalise.i18n-ally
- ms-vscode.vscode-serial-monitor
eyhn.vscode-vibrancyisidor: this extension is deprecated, I suggest to skip. I will test the replacement.- ev3dev.ev3dev-browser