threadDelay: efficiently remove thread delay timer #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unfortunately we cannot track the information on which
ThreadDelay
a thread is blocked in
threadStatus
because it is cleared whena thread is rescheduled. This is too early. In the scenario we are
interested in, the thread is rescheduled when the thread receives an
exception and it's when we interpret the
Throw
we need to know theTimeoutId
of thatthreadDelay
.We add a
threadDelayId
field, which tracks the lastthreadDelay
id.This field only cleared when the thread receives an exception, thus it's
life time is long enough to be useful.