Actions
Backport #1001
closedInterpreter-wide deadlock when native close() is called on fd which is currently being IO#select()ed
Status:
Closed
Assignee:
Description
=begin
details and fix here:
http://coderrr.wordpress.com/2009/01/11/ruby-and-mysqlplus-select-deadlock/
=end
Updated by coderrr (coderrr .) about 15 years ago
=begin
any comments on this?
=end
Updated by rogerdpack (Roger Pack) about 15 years ago
=begin
it might be nice to submit a patch which "fixes" this.
My question, however, is what is the right behavior when a bad socket is discovered? I believe Python raises on the thread that passed it in [not just ignore it], which seems reasonable.
Regardless, looks like a bug to me. Is it exhibited in 1.9?
Thoughts?
=end
Updated by ko1 (Koichi Sasada) about 15 years ago
- Assignee set to akr (Akira Tanaka)
- ruby -v set to 1.8
=begin
=end
Updated by akr (Akira Tanaka) about 15 years ago
- Status changed from Open to Closed
=begin
Thank you for investigating the problem.
However the fix makes IO.select hang when the fd is closed.
I think it is not good behavior.
=end
Updated by shyouhei (Shyouhei Urabe) almost 15 years ago
- Status changed from Closed to Open
- Assignee changed from akr (Akira Tanaka) to shyouhei (Shyouhei Urabe)
=begin
=end
Updated by shyouhei (Shyouhei Urabe) almost 15 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
=begin
Applied in changeset r23577.
=end
Updated by shyouhei (Shyouhei Urabe) almost 15 years ago
- Status changed from Closed to Open
- Assignee changed from shyouhei (Shyouhei Urabe) to wyhaines (Kirk Haines)
=begin
=end
Updated by wyhaines (Kirk Haines) over 14 years ago
- Status changed from Open to Closed
=begin
Applied in r24600.
=end
Actions
Like0
Like0Like0Like0Like0Like0Like0Like0Like0