From: 2851820660@...
Date: 2015-07-09T05:12:05+00:00
Subject: [ruby-core:69912] [CommonRuby - Feature #10371] Use Thread#handle_interrupt in MonitorMixin

Issue #10371 has been updated by 11 22.


http://www.software-rating.com/
http://www.smartlogi.com/ ��
http://www.shareorder.com/  
http://www.gzs168.com/ ��
http://www.aimooimage.com/    
http://www.chinatowngate.net/

http://www.inspiredhypnosis.co.uk/daocplat.html
http://the303plan.com/tibiagoldforsale.html

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

* Author: Andrew Lazarus
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
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/