core: stabilize label updates and revision locking in the asyncResourceGatherer #384
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.
Was able to repro #357 (multiple monitors required i think).
Fixes it on my end.
4509552 reverts the previous approach of adding a timer to re-render, when the resource was not available (#152). It also sets
needsFrame=true
, when render is called butframeCallback
is present (I think not 100% needed but still makes sense)The other 3 commits make sure that
getAssetById
fails less often by removing thebusy
flag and revisioning the locking in the resource gatherer.-fsanitize=thread
is a bit happier regarding the asyncResourceGatherer now. Besides some races withdmas
on startup I think.Closes #367