This looks like a nice cleanup, and fix. Thanks Ivan.
-Chris.
On 05/09/15 15:25, Ivan Gerasimov wrote:
Hi everyone!
The fix didn't bring enough attention back in February for some reason.
So, I'd like to re-request a review.
I've added a regression test, which reliably reproduces a deadlock
Thank you Chris for the review!
Sincerely yours,
Ivan
On 07.09.2015 17:39, Chris Hegarty wrote:
This looks like a nice cleanup, and fix. Thanks Ivan.
-Chris.
On 05/09/15 15:25, Ivan Gerasimov wrote:
Hi everyone!
The fix didn't bring enough attention back in February for some reason.
So,
Hi everyone!
The fix didn't bring enough attention back in February for some reason.
So, I'd like to re-request a review.
I've added a regression test, which reliably reproduces a deadlock on my
local Windows 7 machine.
BUGURL: https://bugs.openjdk.java.net/browse/JDK-8072466
WEBREV:
Can someone help review this fix please?
Comments/suggestions are welcome!
Sincerely yours,
Ivan
On 06.02.2015 20:48, Ivan Gerasimov wrote:
Hello!
There has been a deadlock in jdk-net code noticed on Windows.
In the bug description there's a stack snippet showing that one of the
deadlocked
Hello!
There has been a deadlock in jdk-net code noticed on Windows.
In the bug description there's a stack snippet showing that one of the
deadlocked threads stuck in the native initialization code of
DualStackPlainDatagramSocketImpl and the other -- in initializing of
