Skip to content
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

Don't load the shader cache on a separate thread - all it does is already async #18216

Merged
merged 1 commit into from
Sep 24, 2023

Conversation

hrydgard
Copy link
Owner

Since some time, all the shader cache load has really done in practice is to spawn asynchronous tasks, so it itself runs really quickly.

Gets rid of a mutex and should remove some additional potential for sync bugs, although I think I fixed most of them in the last PR.

We already have to properly handle shutdown of all the async tasks, no need to add another layer of async-ness and locks.

@hrydgard hrydgard added this to the v1.16.4 milestone Sep 24, 2023
@hrydgard hrydgard force-pushed the remove-shader-cache-load-thread branch from c5f0f0c to d31ba39 Compare September 24, 2023 08:53
@hrydgard hrydgard merged commit 559cc60 into master Sep 24, 2023
18 checks passed
@hrydgard hrydgard deleted the remove-shader-cache-load-thread branch September 24, 2023 09:18
hrydgard added a commit that referenced this pull request Oct 3, 2023
Simplify disk-cache-load on GLES as well, for the same reasons as #18216
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant