Skip to content

fix: Make node marking as removable safer #8014

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

Merged
merged 1 commit into from
Aug 6, 2025

Conversation

MatiPl01
Copy link
Member

@MatiPl01 MatiPl01 commented Aug 5, 2025

Summary

This PR aims to fix the following issue #8001.

I was unable to reproduce this issue but I suspect that these lock calls were missing before, which resulted in crashes when the removableShadowNodes_ map was modified while the handleNodeRemovals method in the mount hook was called

@MatiPl01 MatiPl01 force-pushed the @matipl01/safer-removable-nodes-marking branch from 2a3da70 to d6cd77f Compare August 6, 2025 11:38
@MatiPl01 MatiPl01 added this pull request to the merge queue Aug 6, 2025
Merged via the queue into main with commit 31964eb Aug 6, 2025
35 checks passed
@MatiPl01 MatiPl01 deleted the @matipl01/safer-removable-nodes-marking branch August 6, 2025 15:05
MatiPl01 added a commit that referenced this pull request Aug 7, 2025
## Summary

This PR aims to fix the following issue #8001.

I was unable to reproduce this issue but I suspect that these lock calls
were missing before, which resulted in crashes when the
`removableShadowNodes_` map was modified while the `handleNodeRemovals`
method in the mount hook was called
MatiPl01 added a commit that referenced this pull request Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants