Skip to content

Fix #8639 - Concurrency problem in remote profiler communication mechanism #8645

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

Merged
merged 3 commits into from
Jul 14, 2025

Conversation

asfernandes
Copy link
Member

No description provided.

@asfernandes asfernandes linked an issue Jul 9, 2025 that may be closed by this pull request
@asfernandes asfernandes force-pushed the work/gh-8639/profiler-cancel-boost-ipc branch from a281650 to 3241a45 Compare July 9, 2025 14:27
@asfernandes asfernandes marked this pull request as ready for review July 10, 2025 11:45
@asfernandes asfernandes changed the title Fix #8639 - Concurrency problem in remote profiler communication mechanism using boost/interprocess Fix #8639 - Concurrency problem in remote profiler communication mechanism Jul 13, 2025
@asfernandes asfernandes force-pushed the work/gh-8639/profiler-cancel-boost-ipc branch from 52af692 to d69eaf5 Compare July 14, 2025 22:28
@asfernandes asfernandes merged commit 06992a9 into master Jul 14, 2025
36 checks passed
@asfernandes asfernandes deleted the work/gh-8639/profiler-cancel-boost-ipc branch July 14, 2025 22:31
@dyemanov
Copy link
Member

Out of curiosity, how do you recover from the shared spinlock being "locked" but the process holding that spinlock crashed? I'm mostly worried about CS. So far we were using shared mutexes because they get automatically "unlocked" in such scenario.

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.

Concurrency problem in remote profiler communication mechanism
2 participants