On 02/25/2016 11:48 PM, Tony Printezis wrote: > Has anyone identified this issue before?
Hm, there is a blast from the past: https://bugs.openjdk.java.net/browse/JDK-4806753 In comments there, Mark suggests a patch that apparently handles multiple coders. I wonder where did that go. Also, Martin Buchholz is still an assignee there :) > We believe that caching a small number of coders per thread (instead > of just one) could avoid this unnecessary churn. We’ll be happy to > contribute such a fix if there’s interest in getting it accepted. Yes, this seems important. Thanks, -Aleksey
