-
Notifications
You must be signed in to change notification settings - Fork 369
Open
Labels
[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended
Description
Prerequisites
- I have carried out troubleshooting steps and I believe I have found a bug.
- I have searched for similar bugs in both open and closed issues and cannot find a duplicate.
Describe the bug
The Asyncify web version of Playground doesn't catch wasm crashes while executing a PHP runtime function.
As a result, the error isn't rethrown and won't be collected by the logger or show the error modal on the website.
Expected behavior
An Asyncify wasm crash should be caught while executing a PHP runtime function and rethrown, resulting in the error modal to appear.
Actual behavior
A Unhandled Promise Rejection: RuntimeError: Unreachable code should not be executed (evaluating 'e(...t)') error is thrown in the browser console.
Steps to reproduce
- Open a browser that uses Asyincify (Safari)
- Trigger a wasm crash in Playground by opening this URL
- See the error in the browser console
- See that the error modal didn't load
Isolating the problem
- I have deactivated other plugins and confirmed this bug occurs when only this plugin is active.
- This bug happens with a default WordPress theme active.
- I can reproduce this bug consistently using the steps above.
Metadata
Metadata
Assignees
Labels
[Type] BugAn existing feature does not function as intendedAn existing feature does not function as intended