Issue 20219 - Idle D programs keep consuming CPU in Gcx.scanBackground #2802
Conversation
Thanks for your pull request, @rainers! Bugzilla references
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub fetch digger
dub run digger -- build "stable + druntime#2802" |
|
Oops, missed to add "fix" when copying the title from the issue. Amended.
I guess the next version (2.089) will start from master anyway. Or are we already past that point?
All the existing tests run with the parallel marking, so the test for correct termination should be that the test suite doesn't run longer than before. Actually testing whether there are too many spurious wake ups of the background threads might be a bit invasive. |
Thanks.
not sure, but targeting stable will make it into the betas if nothing else. I only asked because this is marked regression.
Thats what I though was going to be the case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Is the Buildkite Ocean failure related?
Maybe. Both failing tests are using fork()... |
Speaking of |
I tried it and here's what I found: |
Rebased to stable to pick up #2805 |
…round background scan threads now wait indefinitely, with termination continuously triggering the condition until all threads have woken up
background scan threads now wait indefinitely, with termination continuously triggering the condition until all threads have woken up