Don't reuse the same list for _get_property_list()
#1904
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to work around an issue where we need to keep the
List<PropertyInfo>for_get_property_list()alive until the data it contains isn't needed anymore, we've been reusing the sameList<PropertyInfo>.This works fine in a single-threaded scenario, but when multiple threads are involved, they'll stomp all over the list at the same time.
This PR makes it so that we aren't reusing the same
List<PropertyInfo>, but instead, allocating a new one each time.The tricky part is that we need to hang onto a pointer to it, so that we can free it when we're done. However, Godot will only pass us the
GDExtensionPropertyInfo *and doesn't let us stash any extra data. So, this PR uses the padding that's added byMemory::alloc_static()to stash the pointer in the same place that we usually put the element count when doingmemnew_arr().This is a little hacky, and it would be better if Godot gave us a place to stash some extra data instead, but this does seem to work in my testing :-)
Fixes godotengine/godot#115017