-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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 hold raw RuntimeScheduler pointer in BufferedRuntimeExecutor #46542
Conversation
This pull request was exported from Phabricator. Differential Revision: D62748768 |
1 similar comment
This pull request was exported from Phabricator. Differential Revision: D62748768 |
…acebook#46542) Summary: Pull Request resolved: facebook#46542 If `bufferedRuntimeExecutor_` is referenced beyond the lifetime of the ReactInstance, it may point to invalid memory. RuntimeScheduler already holds weak references to the actual runtime, so it's safe to retain that instead. Changelog: [Internal] Reviewed By: rshest Differential Revision: D62748768
059132a
to
6200771
Compare
…acebook#46542) Summary: Pull Request resolved: facebook#46542 If `bufferedRuntimeExecutor_` is referenced beyond the lifetime of the ReactInstance, it may point to invalid memory. RuntimeScheduler already holds weak references to the actual runtime, so it's safe to retain that instead. Changelog: [Internal] Differential Revision: D62748768 Reviewed By: rshest
…acebook#46542) Summary: Pull Request resolved: facebook#46542 If `bufferedRuntimeExecutor_` is referenced beyond the lifetime of the ReactInstance, it may point to invalid memory. RuntimeScheduler already holds weak references to the actual runtime, so it's safe to retain that instead. Changelog: [Internal] Differential Revision: D62748768 Reviewed By: rshest
This pull request was exported from Phabricator. Differential Revision: D62748768 |
…acebook#46542) Summary: Pull Request resolved: facebook#46542 If `bufferedRuntimeExecutor_` is referenced beyond the lifetime of the ReactInstance, it may point to invalid memory. RuntimeScheduler already holds weak references to the actual runtime, so it's safe to retain that instead. Changelog: [Internal] Reviewed By: rshest Differential Revision: D62748768
6200771
to
66ef74d
Compare
…acebook#46542) Summary: Pull Request resolved: facebook#46542 If `bufferedRuntimeExecutor_` is referenced beyond the lifetime of the ReactInstance, it may point to invalid memory. RuntimeScheduler already holds weak references to the actual runtime, so it's safe to retain that instead. Changelog: [Internal] Reviewed By: rshest Differential Revision: D62748768
66ef74d
to
db4be87
Compare
This pull request was exported from Phabricator. Differential Revision: D62748768 |
…acebook#46542) Summary: Pull Request resolved: facebook#46542 If `bufferedRuntimeExecutor_` is referenced beyond the lifetime of the ReactInstance, it may point to invalid memory. RuntimeScheduler already holds weak references to the actual runtime, so it's safe to retain that instead. Changelog: [Internal] Differential Revision: D62748768 Reviewed By: rshest
This pull request has been merged in e27259b. |
This pull request was successfully merged by @javache in e27259b When will my fix make it into a release? | How to file a pick request? |
Summary:
If
bufferedRuntimeExecutor_
is referenced beyond the lifetime of the ReactInstance, it may point to invalid memory. RuntimeScheduler already holds weak references to the actual runtime, so it's safe to retain that instead.Changelog: [Internal]
Differential Revision: D62748768