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.

Sign up for GitHub

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

Jump to bottom

Trace pool usage breaks when tasks migrate #36

Open
comnik opened this issue Jun 9, 2021 · 0 comments
Open

Trace pool usage breaks when tasks migrate #36

comnik opened this issue Jun 9, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@comnik
Copy link
Contributor

comnik commented Jun 9, 2021

Originally identified by @Sacha0 . On 1.7 it seems like tasks can now migrate arbitrarily between threads. This means that the thread on which a derived function call returns is often not the one on which it was called.

This breaks the TraceId approach, which stores an offset into the original thread's trace pool.
@comnik comnik added the bug Something isn't working label Jun 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@comnik