Alan,
There is no test case for this issue and also the attempt to outline the conditions ended with no result. The report is based only on 'WaitForMultipleObjects' code analysis and this fix is an attempt to make the code looks a little more correct.

-Aleksej

On 05/13/2014 02:57 PM, Alan Bateman wrote:

This is debugger's shared memory transport so cc'ing serviceability-dev as that is there this code is maintained.

Is there a test case or any outline of the conditions that cause this? I think that would be useful to understand the issue further.

-Alan

On 13/05/2014 11:46, Aleksej Efimov wrote:
Hi,

Can I have a review for 8032901 bug [1] fix [2]. There is a possible case when 'WaitForMultipleObjects' function can return the WAIT_ABANDONED_0 [3] error value. In such case it's better to release the mutex and return error value. This will prevent other threads to be blocked on abandoned mutex.

Thank you,
Aleksej

[1] https://bugs.openjdk.java.net/browse/JDK-8032901
[2] http://cr.openjdk.java.net/~aefimov/8032901/9/webrev.00/
[3] http://msdn.microsoft.com/en-gb/library/windows/desktop/ms687025(v=vs.85).aspx


Reply via email to