Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
arsatyants opened this issue Mar 5, 2025 · 12 comments · Fixed by #242851
Open

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

arsatyants opened this issue Mar 5, 2025 · 12 comments · Fixed by #242851
Assignees
@deepak1556
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release electron-34-update freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues linux Issues with VS Code on Linux
Milestone
February 2025 Rec...

Comments

@arsatyants
Copy link

arsatyants commented Mar 5, 2025 •
edited
Loading

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:

  1. update February 2025 (version 1.98) code_1.98.0-1741123840_arm64.deb
  2. 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
Copy link

yuxqiu commented Mar 5, 2025

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
Copy link

@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
Copy link

Wangijun commented Mar 6, 2025

终端进程“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
Copy link
Author

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.

@lramos15 lramos15 assigned deepak1556 and rzhao271 and unassigned dbaeumer Mar 6, 2025
@julienrbrt
Copy link

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.

@julienrbrt julienrbrt mentioned this issue Mar 6, 2025
Closed
@deepak1556
Copy link
Collaborator

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

@deepak1556 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
Copy link
Collaborator

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

@yuxqiu
Copy link

yuxqiu commented Mar 6, 2025

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 deepak1556 mentioned this issue Mar 6, 2025
Merged
@deepak1556 deepak1556 added the bug Issue identified by VS Code Team member as probable bug label Mar 6, 2025
@deepak1556 deepak1556 added this to the March 2025 milestone Mar 6, 2025
@vs-code-engineering 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 drmikecooke mentioned this issue Mar 8, 2025
Closed
@deepak1556
Copy link
Collaborator

Reopening to mark as candidate for 1.98.1 release.

@deepak1556 deepak1556 reopened this Mar 10, 2025
@deepak1556 deepak1556 added the candidate Issue identified as probable candidate for fixing in the next release label Mar 10, 2025
@vs-code-engineering vs-code-engineering bot removed the insiders-released Patch has been released in VS Code Insiders label Mar 10, 2025
@deepak1556 deepak1556 changed the title VS Code continuously crashed after last update(February 2025 (version 1.98)) Crash on linux with 16KB page size from Electron 34 update Mar 10, 2025
@gjsjohnmurray
Copy link
Contributor

@deepak1556 maybe pin this issue until the recovery release lands?

@deepak1556 deepak1556 pinned this issue Mar 10, 2025
@DagBjorndal
Copy link

Crashing for me as well.

@arsatyants
Copy link
Author

release 1.98.1 has the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@deepak1556 deepak1556

Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release electron-34-update freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues linux Issues with VS Code on Linux
Projects
None yet
Milestone
February 2025 Recovery 2
Development

Successfully merging a pull request may close this issue.

fix: crash on linux with 16KB page size microsoft/vscode