-
Notifications
You must be signed in to change notification settings - Fork 24.6k
Make ShadowNodeRegistry thread safe #13994
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
Conversation
As noted in `addRootNode`, ShadowNodeRegistry can be accessed by multiple threads. Make it thread safe to avoid crashes in `UIImplementation` module (e.g. tag cannot be found).
Is there any news on this? |
@bood I tried to find reviewers for this pull request and wanted to ping them to take another look. However, based on the blame information for the files in this pull request I couldn't find any reviewers. This sometimes happens when the files in the pull request are new or don't exist on master anymore. Is this pull request still relevant? If yes could you please rebase? In case you know who has context on this code feel free to mention them in a comment (one person is fine). Thanks for reading and hope you will continue contributing to the project. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions. |
Motivation (required)
As noted in
TODO
ofaddRootNode
, ShadowNodeRegistry can be accessed bymultiple threads. Make it thread safe can avoid crashes in
UIImplementation
module (e.g. tag cannot be found).Fixes #11524 and #10755.
Example of crash stack (0.44.0):
Test Plan (required)
Crash can be re-produced by monkey test. After the fix applied, related crashes are never seen again.