-
Notifications
You must be signed in to change notification settings - Fork 21
2.12.1 dead-locks on some nasty nested Runnables #10169
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
Comments
Imported From: https://issues.scala-lang.org/browse/SI-10169?orig=1 |
@som-snytt said: It works if |
@som-snytt said: The risk increases in 2.12 with lambdas. Besides making
|
@som-snytt said: |
Vladimir Kostyukov (vkostyukov) said: |
This was discovered in Finagle when compiled with Scala 2.12 (see twitter/finagle#581). Turns out some of the threads in the Netty worker pool dead-lock during the initialization with Scala 2.12.1 but work fine with 2.11.7.
I tried to simplify the reproducer as much as possible but I want to apologize for its size. It won't probably fit the Jira ticket so I created a self-contained Github repo (see https://github.com/vkostyukov/scala-2-12-1-and-runnable-bug) containing the reproducer.
Here are steps to reproduce the issue:
git clone [email protected]:vkostyukov/scala-2-12-1-and-runnable-bug.git
cd scala-2-12-1-and-runnable-bug
sbt ++2.11.7 run
(program terminates)sbt ++2.12.1 run
(program never terminates)I'm happy to provide more details if needed. My current hand-waving hypothesis is that it's somewhat a combination of (a) weirdly nested runnables used (b) during the class initialization.
The text was updated successfully, but these errors were encountered: