From: nerdrew@...
Date: 2014-10-12T06:44:23+00:00
Subject: [ruby-core:65629] [CommonRuby - Feature #10371] Use Thread#handle_interrupt in MonitorMixin

Issue #10371 has been updated by Andrew Lazarus.


There was an old bug that might have been related: https://bugs.ruby-lang.org/issues/4266

----------------------------------------
Feature #10371: Use Thread#handle_interrupt in MonitorMixin
https://bugs.ruby-lang.org/issues/10371#change-49362

* Author: Andrew Lazarus
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
Now that ruby has Thread#handle_interrupt, MonitorMixin can always unlock the mutex even when a timeout exception is raised.

Currently, if a timeout exception is raised in MonitorMixin#mon_exit at just the wrong time, the @mon_owner is set to nil, but the @mon_mutex is still locked. ThreadError: deadlock; recursive locking is raised the next time the resource is accessed.



-- 
https://bugs.ruby-lang.org/