-
Notifications
You must be signed in to change notification settings - Fork 497
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
[Wisp] Coroutine hangs permanently in AbstractQueuedSynchronizer #236
Labels
bug
Something isn't working
Comments
joeyleeeeeee97
pushed a commit
to joeyleeeeeee97/dragonwell8_jdk
that referenced
this issue
Jul 6, 2021
Summary: In wisp1 we use direct scheduler wakeup instead of park/unpark for coroutine timed-waiting, so for historical reason exists a manual status fix to lazy set status to free. But in wisp2 when timer is waken up by unpark, a PERMITTED may be overwriten and cause problem. Test Plan: com/alibaba/rcm/ Reviewed-by: leiyu, zhengxiaolinX, sanhong.lsh Issue: dragonwell-project/dragonwell8#236
joeyleeeeeee97
pushed a commit
to joeyleeeeeee97/dragonwell8_jdk
that referenced
this issue
Jul 6, 2021
Summary: In wisp1 we use direct scheduler wakeup instead of park/unpark for coroutine timed-waiting, so for historical reason exists a manual status fix to lazy set status to free. But in wisp2 when timer is waken up by unpark, a PERMITTED may be overwriten and cause problem. Test Plan: com/alibaba/rcm/ Reviewed-by: leiyu, zhengxiaolinX, sanhong.lsh Issue: dragonwell-project/dragonwell8#236
joeyleeeeeee97
pushed a commit
to joeyleeeeeee97/dragonwell8_jdk
that referenced
this issue
Jul 8, 2021
Summary: In wisp1 we use direct scheduler wakeup instead of park/unpark for coroutine timed-waiting, so for historical reason exists a manual status fix to lazy set status to free. But in wisp2 when timer is waken up by unpark, a PERMITTED may be overwriten and cause problem. Test Plan: com/alibaba/rcm/ Reviewed-by: leiyu, zhengxiaolinX, sanhong.lsh Issue: dragonwell-project/dragonwell8#236
joeyleeeeeee97
pushed a commit
to joeyleeeeeee97/dragonwell8_jdk
that referenced
this issue
Jul 8, 2021
Summary: In wisp1 we use direct scheduler wakeup instead of park/unpark for coroutine timed-waiting, so for historical reason exists a manual status fix to lazy set status to free. But in wisp2 when timer is waken up by unpark, a PERMITTED may be overwriten and cause problem. Test Plan: com/alibaba/rcm/ Reviewed-by: leiyu, zhengxiaolinX, sanhong.lsh Issue: dragonwell-project/dragonwell8#236
joeyleeeeeee97
pushed a commit
to joeyleeeeeee97/dragonwell8_jdk
that referenced
this issue
Jul 9, 2021
Summary: In wisp1 we use direct scheduler wakeup instead of park/unpark for coroutine timed-waiting, so for historical reason exists a manual status fix to lazy set status to free. But in wisp2 when timer is waken up by unpark, a PERMITTED may be overwriten and cause problem. Test Plan: com/alibaba/rcm/ Reviewed-by: leiyu, zhengxiaolinX, sanhong.lsh Issue: dragonwell-project/dragonwell8#236
joeyleeeeeee97
pushed a commit
to dragonwell-project/dragonwell8_jdk
that referenced
this issue
Jul 9, 2021
Summary: In wisp1 we use direct scheduler wakeup instead of park/unpark for coroutine timed-waiting, so for historical reason exists a manual status fix to lazy set status to free. But in wisp2 when timer is waken up by unpark, a PERMITTED may be overwriten and cause problem. Test Plan: com/alibaba/rcm/ Reviewed-by: leiyu, zhengxiaolinX, sanhong.lsh Issue: dragonwell-project/dragonwell8#236
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
May hangs permanently in rare cases
Steps to Reproduce
Soon we will see few threads are active and most threads are waiting in an illegal state:
Expected behavior
submit thread keep running
JDK version
8.7.7
Execution environment
The text was updated successfully, but these errors were encountered: