Merge VSCode fix to address arm64 electron crash issue

[irontonbrewing]

Due to an electron update related to 16KB page sizes, the arm64 build of VSCode and VSCodium (1.98.2) crashes within 10-20 seconds of launching. This issue was recently addressed by this VSCode commit and should be merged ASAP, at least for the arm64 line.

NOTE: the equivalent command line workaround is to launch the process with the flag --js-flags="--nodecommit_pooled_pages"

[daiyam]

The fix for that issue ships with electron-v34.3.0, VSCodium uses electron-v34.2.0 which doesn't include the fix.
VSCode use a custom build of electron-v34.2.0 which is including the fix.
So a full fix would require that commit, thx.

Are your affected?

[irontonbrewing]

Yes, the application cannot run on Raspberry Pi without this pooled_pages flag. I can confirm passing the flag at the command line fixes it. While a newer version of electron may be the “real” fix, the workaround seems to be this flag, which is being “forced” by the commit I referenced. It’s just a few lines; shouldn’t it be taken for the arm64 build until a newer electron build?

[daiyam]

In few hours, I will update to a new electron and the additional fix.

[irontonbrewing]

Oh I see, nice thank you!

[daiyam]

@irontonbrewing Is the lastest version working?

[irontonbrewing]

Sorry no, still same issue. The "pooled_pages" flag is still necessary to prevent a crash.

Version: 1.98.2
Release: 25078
Commit: c6286962b0f5f2c3ad5e558a439dc3fcfd20b2ac
Date: 2025-03-19T00:33:41.056Z
Electron: 34.3.2
ElectronBuildId: undefined
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Linux arm64 6.6.74+rpt-rpi-2712

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!

[github-actions]

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue.