Actions
Feature #10371
openUse Thread#handle_interrupt in MonitorMixin
Status:
Open
Assignee:
-
Target version:
-
Description
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.
Updated by nerdrew (Andrew Lazarus) about 10 years ago
There was an old bug that might have been related: https://bugs.ruby-lang.org/issues/4266
Updated by hsbt (Hiroshi SHIBATA) almost 3 years ago
- Project changed from 14 to Ruby master
Actions
Like0
Like0Like0