8000 [Bug]: Received signal 11 SEGV_ACCERR 0000000005b5 - Renderer crash · Issue #36832 · electron/electron · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Bug]: Received signal 11 SEGV_ACCERR 0000000005b5 - Renderer crash #36832

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.

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

Closed
3 tasks done
jupnit opened this issue Jan 9, 2023 · 9 comments
Closed
3 tasks done

[Bug]: Received signal 11 SEGV_ACCERR 0000000005b5 - Renderer crash #36832

jupnit opened this issue Jan 9, 2023 · 9 comments

Comments

@jupnit
Copy link
jupnit commented Jan 9, 2023

Preflight Checklist

Electron Version

22.0.0

What operating system are you using?

macOS

Operating System Version

macOS Monterey 12.6.2

What arch are you using?

arm64 (including Apple Silicon)

Last Known Working Electron version

21.3.3

Expected Behavior

Renderer process should not crash.

Actual Behavior

Renderer process is crashing on upgrade to electron v22. This happens in both Windows and MacOS. App is working fine with last stable electron version 21.3.3.
Unable to debug the exact root cause but we are using [single-spa-angular](https://github.com/single-spa/single-spa-angular) module in our project and this crash happens just after loading single-spa-angular-internals.umd.js script asynchronously.

Using export ELECTRON_ENABLE_STACK_DUMPING=true, I get following log -

Received signal 11 SEGV_ACCERR 0000000005b5
[0x00010d44b530]
[0x00010d3ea190]
[0x00010d44b4b0]
[0x0001b23934a4]
[0x000110a89a2c]
....`

The only reason we want to upgrade to electron v22 is because it comes with bumped version of electron/get to 2.0.0. This version of electron/get has a fix for a security vulnerability as described in this issue. If this can be backported to electron version 21.3.3, we can still continue to use that version.

Testcase Gist URL

No response

Additional Information

Unfortunately, I cannot upload my project or any part of it. I'm hoping people with more experience can point out how to debug this issue. Ideally to identify what's causing the problem.

@jupnit jupnit added the bug 🪲 label Jan 9, 2023
@codebytere codebytere added blocked/need-repro Needs a test case to reproduce the bug platform/macOS 22-x-y labels Jan 9, 2023
@github-actions
Copy link
Contributor
github-actions bot commented Jan 9, 2023

Hello @jupnit. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

@BobSos

This comment was marked as duplicate.

@github-actions github-actions bot removed the blocked/need-repro Needs a test case to reproduce the bug label Jan 16, 2023
@jupnit
Copy link
Author
jupnit commented Jan 18, 2023

Hello,

After further analysis, I found out that this was happening because I had disabled sandboxing for preload -

webPreferences: {
  ....
  sandbox: false
}

When I enable sandbox, I have to remove/replace all Node.Js module usage in preload but otherwise my app works fine.

But strange thing is that the app also works fine with sandbox: false when using electron version 21.3.3.

@ckerr
Copy link
Member
ckerr commented Jan 25, 2023

I'm glad you found a workaround!

Still, Electron shouldn't crash with or without sandboxing. There's nothing actionable in the crash report in the initial description, but @jupnit if you're still interested in this issue, please try isolating the crash further, e.g. with a standalone testcase that maintainers can use to try and reproduce the problem

@ckerr ckerr added blocked/need-repro Needs a test case to reproduce the bug labels Jan 25, 2023
@github-actions
Copy link
Contributor

Hello @jupnit. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

1 similar comment
@github-actions
Copy link
Contributor

Hello @jupnit. Thanks for reporting this and helping to make Electron better!

Would it be possible for you to make a standalone testcase with only t 8000 he code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

Now adding the blocked/need-repro label for this reason. After you make a test case, please link to it in a followup comment. This issue will be closed in 10 days if the above is not addressed.

@ci7lus
Copy link
ci7lus commented Feb 3, 2023

I'm also facing a similar issue, I have created a reproduction. It requires macOS to run a setup script. https://github.com/vivid-lapin/electron-v22-native-module-repro

@github-actions github-actions bot removed the blocked/need-repro Needs a test case to reproduce the bug label Feb 4, 2023
@github-actions
Copy link
Contributor
github-actions bot commented May 6, 2023

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!

@github-actions github-actions bot added the stale label May 6, 2023
@github-actions
Copy link
Contributor
github-actions bot commented Jun 5, 2023

This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants
0