Skip to content

fix: add back fallback wasm-trap handling #47345

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

Open
wants to merge 2 commits into
base: 37-x-y
Choose a base branch
from

Conversation

trop[bot]
Copy link
Contributor

@trop trop bot commented Jun 3, 2025

Backport of #47186

See that PR for details.

Notes: none

@trop trop bot requested a review from a team as a code owner June 3, 2025 13:31
@trop trop bot requested review from codebytere and a team June 3, 2025 13:31
@trop trop bot mentioned this pull request Jun 3, 2025
3 tasks
@trop trop bot added 37-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes labels Jun 3, 2025
trop bot and others added 2 commits June 5, 2025 18:36
Refs https://chromium-review.googlesource.com/c/chromium/src/+/5372409

This change sets up wasm-trap handling for the case where content_shell
has not enabled crash reporting but moves the responsibility to
ElectronRendererClient. The default ContentRendererClient assumes
that crash reporting is enabled (crashpad enabled by default) and does
not set up its own handler.

Co-authored-by: Shelley Vohr <[email protected]>
Co-authored-by: deepak1556 <[email protected]>
@codebytere codebytere force-pushed the trop/37-x-y-bp-fix-add-back-fallback-wasm-trap-handling-1748957490155 branch from 562a8c4 to 475e6c3 Compare June 5, 2025 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
37-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant