Bug #4390

TCPSocket#readline doesn't raise if the socket is #close'd in another thread

Added by Alex Young almost 5 years ago. Updated over 4 years ago.

ruby -v:ruby 1.9.2p136 (2010-12-25 revision 30365) [i686-linux] Backport:


In Ruby 1.8.7-p302, the following code outputs "Success!". On 1.9.2-p136, it hangs at q.pop, because the blocked readline doesn't raise (or, more precisely, it does, I think, but the thread isn't woken up to process it).

require 'socket'
require 'thread'

server = TCPServer.new("localhost", 0)
serv_thread = Thread.new{ server.accept }
sock = TCPSocket.new("localhost", server.addr[1])

q = Queue.new
client_thread = Thread.new{
q.push "OK"
rescue StandardError => e
p e

sleep(0.1) while client_thread.status == "run"
err = q.pop
puts "Success!"

It's not immediately clear which is the correct behaviour, but I'm raising an issue against 1.9.2 on the principle that unless there was a conscious decision to change behaviour, a change indicates that something broke. I should also add that this behaviour is not observed in i386-cygwin.

Related issues

Related to Ruby trunk - Bug #4558: TestSocket#test_closed_read fails after r31230 Closed 04/07/2011


#1 Updated by Nobuyoshi Nakada almost 5 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r30852.
Alex, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

  • thread.c (rb_thread_io_blocking_region): new function to run blocking region with GIL released, for fd.
  • thread.c (rb_thread_fd_close): implement. =end

Also available in: Atom PDF