-
-
Notifications
You must be signed in to change notification settings - Fork 24.3k
Revert "Core: Switch RID_alloc::owns to lock-free"
#114963
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
This reverts commit bdfe854. This caused a regression for GPUParticles3D emitters on macOS arm64, which is proving to be both tricky to reproduce and solve. Other parts of the engine using RID_Owner might be affected too. Given that we're about to release 4.6, reverting might be the safest option at this time, and this optimization can be re-attempted for 4.7. Fixes godotengine#114900.
|
Reverting fixes the problem on my M4 Pro MBP. |
bruvzg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverting it is probably the most reasonable thing to do for 4.6. Since it's not consistently reproducible, it would be hard to validate if any proposed fix is fully working for everyone.
clayjohn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
It's unfortunate to lose this optimization, but we can try again for 4.7
stuartcarnie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can also confirm this fixes the issue on my M4 Max
This reverts commit bdfe854 / PR #112657.
This caused a regression for GPUParticles3D emitters on macOS arm64, which is proving to be both tricky to reproduce and solve. Other parts of the engine using RID_Owner might be affected too.
Given that we're about to release 4.6, reverting might be the safest option at this time, and this optimization can be re-attempted for 4.7.
Before merging this, let's see if the latest attempts in #114937 end up fruitful.
It would also be good for people who can reproduce #114900 to test this revert PR and confirm that it does solve the issue.