[Bug]: Crash SIGSEGV at v8::internal::CppHeap::WriteBarrier(v8::internal::JSObject)

[tn185075]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

24.6.0

What operating system are you using?

Ubuntu

Operating System Version

22.04

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

No crash.

Actual Behavior

electron intermittently crashes after window.location.assign("react/route") which happens in a pop-up created by the main window. We see render-process-gone with exit code 139, and the crash dump has the reference to v8::internal::CppHeap::WriteBarrier(v8::internal::JSObject) with symbols generated for our own electron app.

What could be the cause of crash here? Or Is this a v8 bug to be reported?

Testcase Gist URL

No response

Additional Information

No response

[clavin]

Hi! Thanks for taking the time to report this issue. Here are some notes:

1. It'd help us if you could test out this issue on a recent Electron version, like Electron 30. Unfortunately, Electron 24 is no longer supported and the problem may have been fixed since then.
2. We need a small, contained sample of code that triggers this issue so we can reproduce and investigate this issue. That is what the "Testcase Gist URL" is.

I'm going to mark this issue as blocked for those reasons right now. Once you've addressed the concerns above, please do reply here and update your issue body with new information and we can take another look!

[electron-issue-triage]

Hello @tn185075. 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 Needs a test case to reproduce the bug 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.

[tn185075]

@clavin thanks for taking time out, I will need to isolate the case from our app to provide a reproducible piece of code, which I'll try to. do you recommend upgrading to later version of electron?

[clavin]

Yes, upgrading to Electron 29 or 30 to make sure this crash is still present in recent versions and not just an old crash that may have been fixed already.

[electron-issue-triage]

Unfortunately, without a way to reproduce this issue, we're unable to continue investigation. This issue has been closed and will not be monitored further. If you're able to provide a minimal test case that reproduces this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.