* [ruby-core:65628] [CommonRuby - Feature #10371] [Open] Use Thread#handle_interrupt in MonitorMixin
[not found] <redmine.issue-10371.20141012064148@ruby-lang.org>
@ 2014-10-12 6:41 ` nerdrew
2014-10-12 6:44 ` [ruby-core:65629] [CommonRuby - Feature #10371] " nerdrew
2015-07-09 5:12 ` [ruby-core:69912] " 2851820660
2 siblings, 0 replies; 3+ messages in thread
From: nerdrew @ 2014-10-12 6:41 UTC (permalink / raw
To: ruby-core
Issue #10371 has been reported by Andrew Lazarus.
----------------------------------------
Feature #10371: Use Thread#handle_interrupt in MonitorMixin
https://bugs.ruby-lang.org/issues/10371
* 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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:65629] [CommonRuby - Feature #10371] Use Thread#handle_interrupt in MonitorMixin
[not found] <redmine.issue-10371.20141012064148@ruby-lang.org>
2014-10-12 6:41 ` [ruby-core:65628] [CommonRuby - Feature #10371] [Open] Use Thread#handle_interrupt in MonitorMixin nerdrew
@ 2014-10-12 6:44 ` nerdrew
2015-07-09 5:12 ` [ruby-core:69912] " 2851820660
2 siblings, 0 replies; 3+ messages in thread
From: nerdrew @ 2014-10-12 6:44 UTC (permalink / raw
To: ruby-core
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/
^ permalink raw reply [flat|nested] 3+ messages in thread
* [ruby-core:69912] [CommonRuby - Feature #10371] Use Thread#handle_interrupt in MonitorMixin
[not found] <redmine.issue-10371.20141012064148@ruby-lang.org>
2014-10-12 6:41 ` [ruby-core:65628] [CommonRuby - Feature #10371] [Open] Use Thread#handle_interrupt in MonitorMixin nerdrew
2014-10-12 6:44 ` [ruby-core:65629] [CommonRuby - Feature #10371] " nerdrew
@ 2015-07-09 5:12 ` 2851820660
2 siblings, 0 replies; 3+ messages in thread
From: 2851820660 @ 2015-07-09 5:12 UTC (permalink / raw
To: ruby-core
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/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-07-09 4:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <redmine.issue-10371.20141012064148@ruby-lang.org>
2014-10-12 6:41 ` [ruby-core:65628] [CommonRuby - Feature #10371] [Open] Use Thread#handle_interrupt in MonitorMixin nerdrew
2014-10-12 6:44 ` [ruby-core:65629] [CommonRuby - Feature #10371] " nerdrew
2015-07-09 5:12 ` [ruby-core:69912] " 2851820660
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).