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

[Bug] WispTask re-wakeup wasting a lot of CPU #262

Closed
yuleil opened this issue Sep 26, 2021 · 0 comments
Closed

[Bug] WispTask re-wakeup wasting a lot of CPU #262

yuleil opened this issue Sep 26, 2021 · 0 comments
Assignees
@yuleil
Labels
bug Something isn't working

Comments

@yuleil
Copy link
Collaborator

yuleil commented Sep 26, 2021

Description
WispTask re-wakeup wasting a lots of CPU

Steps to Reproduce
Steps to reproduce the behavior:

  1. A coroutine exits
  2. coroutine was wakeup for some unknown reason was
  3. Switching to the exiting coroutine failed
  4. re-execute wakeup
  5. to step 2

Expected behavior
A clear and concise description of what you expected to happen.

JDK version
The output of java -version command

Execution environment

  • OS and version:
  • CPU model:
  • Number of CPU cores:
  • Size of physical memory:
  • Inside Linux container?
    • Linux container name (docker, pouch, etc):
    • Linux container version:
@yuleil yuleil changed the title [Bug] WispTask re-wakeup wasting a lots of CPU [Bug] WispTask re-wakeup wasting a lot of CPU Sep 26, 2021
yuleil added a commit to yuleil/dragonwell8_jdk that referenced this issue Sep 26, 2021
@yuleil
[Wisp] Exited coroutine should not be re-wakeuped
802a9e6 
Summary: re-wakeup a exited coroutine can waste a lot of CPU

Test Plan: Verify on a reproducible environment

Reviewed-by: joeylee, zhenxiaolinX

Issue: dragonwell-project/dragonwell8#262
@yuleil yuleil mentioned this issue Sep 26, 2021
Merged
@yuleil yuleil self-assigned this Sep 26, 2021
@yuleil yuleil added the bug Something isn't working label Sep 26, 2021
yuleil added a commit to dragonwell-project/dragonwell8_jdk that referenced this issue Sep 26, 2021
@yuleil
[Wisp] Exited coroutine should not be re-wakeuped
dae4180 
Summary: re-wakeup a exited coroutine can waste a lot of CPU

Test Plan: Verify on a reproducible environment

Reviewed-by: joeylee, zhenxiaolinX

Issue: dragonwell-project/dragonwell8#262
@yuleil yuleil closed this as completed Sep 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yuleil yuleil

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yuleil