Crash on linux with 16KB page size from Electron 34 update #242742

arsatyants · 2025-03-05T22:48:23Z

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.98
OS Version: Linux pi5-ssd 6.6.74+rpt-rpi-2712 1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux

Steps to Reproduce:

update February 2025 (version 1.98) code_1.98.0-1741123840_arm64.deb
start and wait 10 sec

screen message::::

The window terminated unexpectedly(reason 'crashed', code: '5')

terminal output after crash:::

[main 2025-03-05T22:41:50.284Z] update#setState idle
[main 2025-03-05T22:41:52.553Z] CodeWindow: renderer process gone (reason: crashed, code: 5)
[main 2025-03-05T22:41:53.095Z] Extension host with pid 15010 exited with code: 0, signal: unknown.
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at s.send (node:electron/js2c/browser_init:2:93065)
at _.send (node:electron/js2c/browser_init:2:76113)
at Iw.send (file:///usr/share/code/resources/app/out/main.js:33:23069)
at wf.p (file:///usr/share/code/resources/app/out/main.js:31:19452)
at wf.o (file:///usr/share/code/resources/app/out/main.js:31:19417)
at wf.m (file:///usr/share/code/resources/app/out/main.js:31:19279)
at qo.value (file:///usr/share/code/resources/app/out/main.js:32:265)
at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
at I.C (file:///usr/share/code/resources/app/out/main.js:30:2443)
at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2660)
at qo.value (file:///usr/share/code/resources/app/out/main.js:43:13058)
at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2591)
at ForkUtilityProcess.T (file:///usr/share/code/resources/app/out/main.js:28:7328)
at ForkUtilityProcess.emit (node:events:518:28)
at ForkUtilityProcess.a.emit (node:electron/js2c/browser_init:2:71917)
Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed
at s.send (node:electron/js2c/browser_init:2:93065)
at _.send (node:electron/js2c/browser_init:2:76113)
at Iw.send (file:///usr/share/code/resources/app/out/main.js:33:23069)
at wf.p (file:///usr/share/code/resources/app/out/main.js:31:19452)
at wf.o (file:///usr/share/code/resources/app/out/main.js:31:19417)
at wf.m (file:///usr/share/code/resources/app/out/main.js:31:19279)
at s.then.Error.m.id (file:///usr/share/code/resources/app/out/main.js:31:20206)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

yuxqiu · 2025-03-05T23:00:53Z

Same. I can reproduce it with all extensions disabled on Fedora aarch64.

The error message I got is: The window terminated unexpectedly (reason 'crashed', code: '133').

The following is the log before crashing:

Error sending from webFrameMain:  Error: Render frame was disposed before WebFrameMain could be accessed
    at s.send (node:electron/js2c/browser_init:2:93065)
    at _.send (node:electron/js2c/browser_init:2:76113)
    at Iw.send (file:///usr/share/code/resources/app/out/main.js:33:23069)
    at wf.p (file:///usr/share/code/resources/app/out/main.js:31:19452)
    at wf.o (file:///usr/share/code/resources/app/out/main.js:31:19417)
    at wf.m (file:///usr/share/code/resources/app/out/main.js:31:19279)
    at qo.value (file:///usr/share/code/resources/app/out/main.js:32:265)
    at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
    at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2591)
    at qo.value (file:///usr/share/code/resources/app/out/main.js:28:5077)
    at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
    at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2591)
    at qo.value (file:///usr/share/code/resources/app/out/main.js:28:4893)
    at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
    at I.C (file:///usr/share/code/resources/app/out/main.js:30:2443)
    at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2660)
    at k4.deregisterLogger (file:///usr/share/code/resources/app/out/main.js:35:18382)
    at k4.deregisterLogger (file:///usr/share/code/resources/app/out/main.js:50:48713)
    at k4.deregisterLoggers (file:///usr/share/code/resources/app/out/main.js:50:49332)
    at oc.dispose (file:///usr/share/code/resources/app/out/main.js:69:2235)
    at qo.value (file:///usr/share/code/resources/app/out/main.js:68:46757)
    at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
    at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2591)
    at BrowserWindow.T (file:///usr/share/code/resources/app/out/main.js:28:7328)
    at BrowserWindow.emit (node:events:530:35)
    at oc.yb (file:///usr/share/code/resources/app/out/main.js:68:55641)
    at oc.xb (file:///usr/share/code/resources/app/out/main.js:68:55125)
    at MessagePortMain.postMessage (node:electron/js2c/browser_init:2:106820)
    at Object.postMessage (file:///usr/share/code/resources/app/out/main.js:33:24508)
    at Ow.send (file:///usr/share/code/resources/app/out/main.js:33:24080)
    at wf.p (file:///usr/share/code/resources/app/out/main.js:31:19452)
    at wf.o (file:///usr/share/code/resources/app/out/main.js:31:19417)
    at wf.m (file:///usr/share/code/resources/app/out/main.js:31:19279)
    at qo.value (file:///usr/share/code/resources/app/out/main.js:32:265)
    at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
    at I.C (file:///usr/share/code/resources/app/out/main.js:30:2443)
    at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2660)
    at file:///usr/share/code/resources/app/out/main.js:28:6420
    at qo.value (file:///usr/share/code/resources/app/out/main.js:28:5216)
    at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
    at I.C (file:///usr/share/code/resources/app/out/main.js:30:2443)
    at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2660)
    at qo.value (file:///usr/share/code/resources/app/out/main.js:28:5077)
    at I.B (file:///usr/share/code/resources/app/out/main.js:30:2373)
    at I.fire (file:///usr/share/code/resources/app/out/main.js:30:2591)
    at App.T (file:///usr/share/code/resources/app/out/main.js:28:7328)
    at App.emit (node:events:530:35)
    at BrowserWindow.<anonymous> (node:electron/js2c/browser_init:2:12727)
    at BrowserWindow.emit (node:events:530:35)

beingminimal · 2025-03-06T03:31:27Z

@digitarald @dbaeumer @lramos15 A humble request

Our 20-person team is experiencing a critical workflow disruption on Raspberry Pi 5 due to this same VS Code issue, producing the same error code.

We would be extremely thankful to you and the VS Code team for an immediate fix. This is a high-priority issue requiring urgent attention. Thanks.

Wangijun · 2025-03-06T03:55:15Z

终端进程“C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe”已终止，退出代码: -1073741510。

版本: 1.98.0 (user setup)
提交: 6609ac3
日期: 2025-03-04T21:06:18.612Z
Electron: 34.2.0
ElectronBuildId: 11044223
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Windows_NT x64 10.0.26100

arsatyants · 2025-03-06T13:30:02Z

Hi @dbaeumer. This blocker is really showstopper. It would be a huge thanks from me if you say the date of new release with the fix.

julienrbrt · 2025-03-06T20:40:29Z

I am encountering this issue as well on Fedora Asahi. Difference is I am getting error code 133. Impossible to exit as well, I need to SIGKILL it.

deepak1556 · 2025-03-06T22:37:27Z

Can you share the crash dump following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

deepak1556 · 2025-03-06T22:41:50Z

Can you also confirm if launching with --js-flags="--nodecommit_pooled_pages" addresses the crash. Very likely related to electron/electron#45560

yuxqiu · 2025-03-06T22:50:57Z

Can you also confirm if launching with --js-flags="--nodecommit_pooled_pages" addresses the crash. Very likely related to electron/electron#45560

I can confirm this fixes the crash on Fedora Asahi (no crash in the last 5 mins).

deepak1556 · 2025-03-10T03:39:13Z

Reopening to mark as candidate for 1.98.1 release.

simonkurtz-MSFT · 2025-03-14T13:21:37Z

Thank you, @deepak1556! When an update rolls into Insider, and if this issue is tagged, I'll try again and update with results. Appreciate all you do!

vtkacik45 · 2025-03-14T16:19:52Z

there is a lot of people that use the visual studio they need to clarify/ verify that the next update that they do works before they release it to both locations for windows, Linux, and raspberry pi 5 or what ever people use

RuntimeError5086 · 2025-03-14T18:35:07Z

Using code --js-flags="--nodecommit_pooled_pages" fixes the crash Issue on Version

1.98.2
ddc367ed5c8936efe395cffeec279b04ffd7db78
arm64

but I also have the Issue that most of my extensions except for a few Microsoft ones are not being shown in the Extensions tab, they are also not enabled but they were in the folder. I just looked for the path and now they are all gone.

simonkurtz-MSFT · 2025-03-17T16:25:17Z

@deepak1556, the updated Insiders is no longer crashing for me. Thank you!
For clarity for others, the fix in #80eac34 precedes #5b778ce which is the commit referenced below.

Version: 1.99.0-insider
Commit: 5b778ceb0fd58f9cfebbf5ea071e4ebbae751401
Date: 2025-03-17T11:07:01.837Z
Electron: 34.3.2
ElectronBuildId: 11161073
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

deepak1556 · 2025-03-17T16:32:52Z

Thanks for confirming @simonkurtz-MSFT

vtkacik45 · 2025-03-18T04:09:44Z

i am still unable to use it my raspberry pi 5 it still crashes

gjsjohnmurray · 2025-03-18T06:50:21Z

@vtkacik45 what is the exact version information of the executable you are running?

glpix · 2025-03-18T11:42:06Z

I also have a similar problem:
System : RPI 5
OS : Bookworm - OS and all software up to date on 2025-03-17
VSCODE versions : 1.98.1 or 1.98.2
Crashes on RPI 5 after about 30 seconds
Temporary get round : install VSCODE 1.97.2

Problem appears to be VSCODE fetching update information on 1.98.* or maybe requesting telemetry after 30 seconds.

VSCODE 1.98.*: The update badge appears on above the settings cogwheel, and then VSCODE crashes
VSCODE 1.97.2: The update badge appears on above the settings cogwheel, and VSCODE remains stable

Not examined the data flow with 'wireshark', because at the moment I need to use VSCODE, but it does seem related to a network request, because the RPI 5 receives a stream of ACK's from the Microsoft Azure server at 4.152.45.235

Annie-UK · 2025-03-18T11:48:59Z

I also have a similar problem: System : RPI 5 OS : Bookworm - OS and all software up to date on 2025-03-17 VSCODE versions : 1.98.1 or 1.98.2 Crashes on RPI 5 after about 30 seconds Temporary get round : install VSCODE 1.97.2

Problem appears to be VSCODE fetching update information on 1.98.* or maybe requesting telemetry after 30 seconds.
* VSCODE 1.98.*: The update badge appears on above the settings cogwheel, and then VSCODE crashes

* VSCODE 1.97.2: The update badge appears on above the settings cogwheel, and  VSCODE remains stable
Not examined the data flow with 'wireshark', because at the moment I need to use VSCODE, but it does seem related to a network request, because the RPI 5 receives a stream of ACK's from the Microsoft Azure server at 4.152.45.235

You can stop the crashing on a PI 5 either by adding the flag --js-flags="--nodecommit_pooled_pages" (as stated in a post above) or by adding kernel=kernel8.img to /boot/firmware/config.txt

I have tried both methods and the flag is the best work-a-round so far as you retain full performance of the PI5

glpix · 2025-03-18T12:26:17Z

@Annie-UK
Thanks for the tip.
Tried on another RPI 5, as you indicated the flags option is the best, and probably easiest fix - just updating the code.desktop file. The update badge now flashes on and off, and VSCODE 1.98.2 remains stable!

simonkurtz-MSFT · 2025-03-18T12:40:47Z

I also have a similar problem: System : RPI 5 OS : Bookworm - OS and all software up to date on 2025-03-17 VSCODE versions : 1.98.1 or 1.98.2 Crashes on RPI 5 after about 30 seconds Temporary get round : install VSCODE 1.97.2

Problem appears to be VSCODE fetching update information on 1.98.* or maybe requesting telemetry after 30 seconds.

VSCODE 1.98.*: The update badge appears on above the settings cogwheel, and then VSCODE crashes

VSCODE 1.97.2: The update badge appears on above the settings cogwheel, and VSCODE remains stable

Not examined the data flow with 'wireshark', because at the moment I need to use VSCODE, but it does seem related to a network request, because the RPI 5 receives a stream of ACK's from the Microsoft Azure server at 4.152.45.235

You can also install Code Insiders to verify the forthcoming general release fixes this. Please see my comment above for details.

vtkacik45 · 2025-03-19T03:06:48Z

1.98.2
ddc367e
arm64

gjsjohnmurray · 2025-03-19T06:49:27Z

@vtkacik45
Workarounds for your version are given above in #242742 (comment) and fix is in 1.99 Insiders.

juniorHn89 · 2025-03-19T17:10:49Z

También tengo un problema similar: Sistema: RPI 5 SO: Bookworm - SO y todo el software actualizados el 17/03/2025 Versiones de VSCODE: 1.98.1 o 1.98.2 Se bloquea en RPI 5 después de unos 30 segundos Solución temporal: instalar VSCODE 1.97.2
El problema parece ser que VSCODE obtiene información de actualización en 1.98.* o tal vez solicita telemetría después de 30 segundos.
* VSCODE 1.98.*: The update badge appears on above the settings cogwheel, and then VSCODE crashes

* VSCODE 1.97.2: The update badge appears on above the settings cogwheel, and  VSCODE remains stable
No he examinado el flujo de datos con 'wireshark', porque en este momento necesito usar VSCODE, pero parece estar relacionado con una solicitud de red, porque el RPI 5 recibe un flujo de ACK del servidor Microsoft Azure en 4.152.45.235
Puedes detener el bloqueo en un PI 5 agregando el indicador --js-flags="--nodecommit_pooled_pages" (como se indica en una publicación anterior) o agregando kernel=kernel8.img a /boot/firmware/config.txt

He probado ambos métodos y la bandera es la mejor solución hasta ahora, ya que conserva el rendimiento completo del PI5.

a mi me funciono agregando la opcion 2 kernel=kernel8.img*

juniorHn89 · 2025-03-19T17:11:36Z

También tengo un problema similar: Sistema: RPI 5 SO: Bookworm - SO y todo el software actualizados el 17/03/2025 Versiones de VSCODE: 1.98.1 o 1.98.2 Se bloquea en RPI 5 después de unos 30 segundos Solución temporal: instalar VSCODE 1.97.2
El problema parece ser que VSCODE obtiene información de actualización en 1.98.* o tal vez solicita telemetría después de 30 segundos.
* VSCODE 1.98.*: The update badge appears on above the settings cogwheel, and then VSCODE crashes

* VSCODE 1.97.2: The update badge appears on above the settings cogwheel, and  VSCODE remains stable
No he examinado el flujo de datos con 'wireshark', porque en este momento necesito usar VSCODE, pero parece estar relacionado con una solicitud de red, porque el RPI 5 recibe un flujo de ACK del servidor Microsoft Azure en 4.152.45.235
Puedes detener el bloqueo en un PI 5 agregando el indicador --js-flags="--nodecommit_pooled_pages" (como se indica en una publicación anterior) o agregando kernel=kernel8.img a /boot/firmware/config.txt
He probado ambos métodos y la bandera es la mejor solución hasta ahora, ya que conserva el rendimiento completo del PI5.
a mi me funciono agregando la opción 2 kernel=kernel8.img *

Muchas Gracias!!

dylanmtaylor · 2025-03-24T01:00:03Z

@vtkacik45 Workarounds for your version are given above in #242742 (comment) and fix is in 1.99 Insiders.

I think I am possibly hitting this same issue in #244404, I will try 1.99 Insiders.

vs-code-engineering bot added the triage-needed label Mar 5, 2025

vs-code-engineering bot assigned dbaeumer Mar 5, 2025

lramos15 assigned deepak1556 and rzhao271 and unassigned dbaeumer Mar 6, 2025

lramos15 removed the triage-needed label Mar 6, 2025

julienrbrt mentioned this issue Mar 6, 2025

Crash on Fedora Asahi after 1.98 update #242843

Closed

deepak1556 unassigned rzhao271 Mar 6, 2025

deepak1556 added freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues linux Issues with VS Code on Linux labels Mar 6, 2025

deepak1556 mentioned this issue Mar 6, 2025

fix: crash on linux with 16KB page size #242851

Merged

deepak1556 added the bug Issue identified by VS Code Team member as probable bug label Mar 6, 2025

deepak1556 added this to the March 2025 milestone Mar 6, 2025

deepak1556 closed this as completed in #242851 Mar 7, 2025

vs-code-engineering bot added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Mar 7, 2025

drmikecooke mentioned this issue Mar 8, 2025

**The window terminated unexpectedly (reason: ‘crashed’, code: ‘5’)** #242773

Closed

deepak1556 reopened this Mar 10, 2025

deepak1556 added the candidate Issue identified as probable candidate for fixing in the next release label Mar 10, 2025

vs-code-engineering bot removed the insiders-released Patch has been released in VS Code Insiders label Mar 10, 2025

deepak1556 modified the milestones: February 2025 Recovery 2, March 2025 Mar 14, 2025

deepak1556 mentioned this issue Mar 14, 2025

Crash code 5 on raspberry pi 5 #242844

Closed

deepak1556 removed the candidate Issue identified as probable candidate for fixing in the next release label Mar 14, 2025

deepak1556 mentioned this issue Mar 14, 2025

fix: pass nodecommit_pooled_pages for the renderer #243581

Merged

gjsjohnmurray mentioned this issue Mar 16, 2025

Visual Studio Code 1.98 on raspberry pi 5 #243689

Closed

deepak1556 closed this as completed Mar 17, 2025

deepak1556 added the verified Verification succeeded label Mar 17, 2025

deepak1556 mentioned this issue Mar 18, 2025

arm64: Electron process crashes #243789

Closed

This was referenced Mar 24, 2025

VSCode is crashing with error 133 on Fedora Asahi Remix 42 #244404

Closed

code >= 1.98 crashes on startup on Fedora 41 aarch64 when launched in Wayland rendering mode #244818

Closed

Raspberry PI 64 Bit Constant Code 5 Crash #244898

Closed

This was referenced Apr 3, 2025

Crashes every ~10-30s with code 5 #245410

Closed

The window terminated unexpectedly (reason: 'crashed', code:'5') #244325

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Crash on linux with 16KB page size from Electron 34 update #242742

Crash on linux with 16KB page size from Electron 34 update #242742

arsatyants commented Mar 5, 2025 •

edited

Loading

yuxqiu commented Mar 5, 2025

beingminimal commented Mar 6, 2025

Wangijun commented Mar 6, 2025

arsatyants commented Mar 6, 2025

julienrbrt commented Mar 6, 2025

deepak1556 commented Mar 6, 2025

deepak1556 commented Mar 6, 2025

yuxqiu commented Mar 6, 2025

deepak1556 commented Mar 10, 2025

simonkurtz-MSFT commented Mar 14, 2025

vtkacik45 commented Mar 14, 2025

RuntimeError5086 commented Mar 14, 2025

simonkurtz-MSFT commented Mar 17, 2025

deepak1556 commented Mar 17, 2025

vtkacik45 commented Mar 18, 2025

gjsjohnmurray commented Mar 18, 2025

glpix commented Mar 18, 2025

Annie-UK commented Mar 18, 2025

glpix commented Mar 18, 2025

simonkurtz-MSFT commented Mar 18, 2025

vtkacik45 commented Mar 19, 2025

gjsjohnmurray commented Mar 19, 2025

juniorHn89 commented Mar 19, 2025

juniorHn89 commented Mar 19, 2025

dylanmtaylor commented Mar 24, 2025

Crash on linux with 16KB page size from Electron 34 update #242742

Crash on linux with 16KB page size from Electron 34 update #242742

Comments

arsatyants commented Mar 5, 2025 • edited Loading

yuxqiu commented Mar 5, 2025

beingminimal commented Mar 6, 2025

Wangijun commented Mar 6, 2025

arsatyants commented Mar 6, 2025

julienrbrt commented Mar 6, 2025

deepak1556 commented Mar 6, 2025

deepak1556 commented Mar 6, 2025

yuxqiu commented Mar 6, 2025

deepak1556 commented Mar 10, 2025

simonkurtz-MSFT commented Mar 14, 2025

vtkacik45 commented Mar 14, 2025

RuntimeError5086 commented Mar 14, 2025

simonkurtz-MSFT commented Mar 17, 2025

deepak1556 commented Mar 17, 2025

vtkacik45 commented Mar 18, 2025

gjsjohnmurray commented Mar 18, 2025

glpix commented Mar 18, 2025

Annie-UK commented Mar 18, 2025

glpix commented Mar 18, 2025

simonkurtz-MSFT commented Mar 18, 2025

vtkacik45 commented Mar 19, 2025

gjsjohnmurray commented Mar 19, 2025

juniorHn89 commented Mar 19, 2025

juniorHn89 commented Mar 19, 2025

dylanmtaylor commented Mar 24, 2025

arsatyants commented Mar 5, 2025 •

edited

Loading