Skip to content

Make DurationSignalTracker run in main thread rather than private one #239

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

Closed
wants to merge 1 commit into from

Conversation

Jeehut
Copy link
Contributor

@Jeehut Jeehut commented Mar 23, 2025

Fixes #237.

Note: Previously, we were blocking the main thread and waiting for a background thread to execute the code, which was an unnecessary thread switch that only added overhead without any added safety. This avoids that.

@Jeehut
Copy link
Contributor Author

Jeehut commented Mar 24, 2025

After seeing and testing this "fix", the author of #237 concluded that there was actually no issue after all with our implementation and that it's probably more resilient. So I'm closing this PR without merging.

@Jeehut Jeehut closed this Mar 24, 2025
@Jeehut Jeehut removed the request for review from winsmith March 24, 2025 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MainActor-only durationSignal API with unnecessary GCD queue overhead
1 participant