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

Confine context-specific state to the thread in UndispatchedCoroutine… #3155

Merged
merged 3 commits into from Feb 1, 2022
Merged

Confine context-specific state to the thread in UndispatchedCoroutine… #3155

merged 3 commits into from Feb 1, 2022

Commits on Jan 25, 2022

  1. Confine context-specific state to the thread in UndispatchedCoroutine… 

    … in order to avoid state interference when the coroutine is updated concurrently.

Concurrency is inevitable in this scenario: when the coroutine that has UndispatchedCoroutine as its completion suspends, we have to clear the thread context, but while we are doing so, concurrent resume of the coroutine could've happened that also ends up in save/clear/update context

Fixes #2930
    @qwwdfsad
    qwwdfsad committed Jan 25, 2022
    Copy the full SHA
    007b541 View commit details
    Browse the repository at this point in the history

Commits on Feb 1, 2022

  1. Update kotlinx-coroutines-core/jvm/test/ThreadLocalStressTest.kt 

    Co-authored-by: dkhalanskyjb <52952525+dkhalanskyjb@users.noreply.github.com>
    @qwwdfsad @dkhalanskyjb
    qwwdfsad and dkhalanskyjb committed Feb 1, 2022
    Copy the full SHA
    0d4b132 View commit details
    Browse the repository at this point in the history

  2. Update kotlinx-coroutines-core/jvm/test/ThreadLocalStressTest.kt 

    Co-authored-by: dkhalanskyjb <52952525+dkhalanskyjb@users.noreply.github.com>
    @qwwdfsad @dkhalanskyjb
    qwwdfsad and dkhalanskyjb committed Feb 1, 2022
    Copy the full SHA
    217fa43 View commit details
    Browse the repository at this point in the history