-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Do not create RuntimeExecutor on non-JSI executors #38125
Conversation
This pull request was exported from Phabricator. Differential Revision: D47124234 |
Base commit: 3a912a3 |
Summary: Pull Request resolved: facebook#38125 On Android, when using the remote debugging feature (using legacy websockets), it's not safe to assume we can get a `jsi::Runtime` from `JSExecutor`. Changelog: [General][Fixed] Android does't crash when using remote debugger Reviewed By: NickGerleman Differential Revision: D47124234 fbshipit-source-id: b63d9eb5f1d7410f8150340dcd226e9317a2bfdc
1e65f84
to
d5902a9
Compare
This pull request was exported from Phabricator. Differential Revision: D47124234 |
1 similar comment
This pull request was exported from Phabricator. Differential Revision: D47124234 |
Summary: Pull Request resolved: facebook#38125 On Android, when using the remote debugging feature (using legacy websockets), it's not safe to assume we can get a `jsi::Runtime` from `JSExecutor`. Changelog: [General][Fixed] Android does't crash when using remote debugger Reviewed By: NickGerleman Differential Revision: D47124234 fbshipit-source-id: c178915af327604d12c48b1b472ad624a7b75e94
d5902a9
to
3078097
Compare
This pull request was exported from Phabricator. Differential Revision: D47124234 |
Summary: Pull Request resolved: facebook#38125 On Android, when using the remote debugging feature (using legacy websockets), it's not safe to assume we can get a `jsi::Runtime` from `JSExecutor`. Changelog: [General][Fixed] Android does't crash when using remote debugger Reviewed By: NickGerleman Differential Revision: D47124234 fbshipit-source-id: 45ccc2544f104223efde1bec44e11b9cdfc1de52
3078097
to
1dedc83
Compare
Summary: Pull Request resolved: facebook#38125 On Android, when using the remote debugging feature (using legacy websockets), it's not safe to assume we can get a `jsi::Runtime` from `JSExecutor`. Changelog: [General][Fixed] Android does't crash when using remote debugger Reviewed By: NickGerleman Differential Revision: D47124234 fbshipit-source-id: d6e93c760174361940d53fe8c2ebf4685d8cf8ae
This pull request was exported from Phabricator. Differential Revision: D47124234 |
1dedc83
to
a34c48f
Compare
This pull request was successfully merged by @javache in 0fe5ffd. When will my fix make it into a release? | Upcoming Releases |
Summary: Pull Request resolved: facebook#38125 On Android, when using the remote debugging feature (using legacy websockets), it's not safe to assume we can get a `jsi::Runtime` from `JSExecutor`. Changelog: [General][Fixed] Android does't crash when using remote debugger Reviewed By: NickGerleman Differential Revision: D47124234 fbshipit-source-id: 0542da1aca5d411964e3a0833f4c48428ed90c91
…acebook#38142) Co-authored-by: Pieter De Baets <pieterdb@meta.com> resolved: facebook#38125
Summary:
On Android, when using the remote debugging feature (using legacy websockets), it's not safe to assume we can get a
jsi::Runtime
fromJSExecutor
.Changelog: [General][Fixed] Android does't crash when using remote debugger
Differential Revision: D47124234