[1.9.x] Fix dead lock between LoggerContext
and Terminal
#7191
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.
Using
sbtn
I found a deadlock betweenLoggerContext
andTerminal
:The
main
thread locks the list ofconsoleAppenders
inLoggerContext
then it tries to lock theTerminal
to write to it.The
sbt-task-progress-report-thread
locks theTerminal
to compute the progress report. When computing the progress report it tries to log something using theconsoleAppenders
inLoggerContext
.To fix this deadlock we can use a
AtomicReference[scala.Vector[???]]
instead ofjava.util.Vector[???]
.Here the thread dump of the deadlock: