From: Tomoyuki Chikanaga Date: 2011-11-04T23:46:27+09:00 Subject: [ruby-core:40740] [ruby-trunk - Bug #5539] Readline.readline() blocks all threads Issue #5539 has been updated by Tomoyuki Chikanaga. File readline.patch added Category set to ext Assignee set to Kouji Takao I can reproduce the issue wiht readline configured with --enable-libedit option. I wrote a patch. Takao san, how about this patch? Description of the patch: libedit check rl_getc_function only when rl_initialize() is called. And using_history() may call rl_initialize(). So rl_getc_function should be assigned before calling using_history(). Thanks, ---------------------------------------- Bug #5539: Readline.readline() blocks all threads http://redmine.ruby-lang.org/issues/5539 Author: Christopher Huff Status: Open Priority: Normal Assignee: Kouji Takao Category: ext Target version: ruby -v: ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin10.8.0] The standard library Readline.readline() function blocks the thread it's called from without unlocking the VM, thus blocking all threads. This code demonstrates the problem: require 'pp' t = Thread.new {10.times {|x| puts x; sleep 1}} while(buf = Readline.readline) p buf if(buf == 'q') break end end Thread t will be blocked by the readline call, numbers being printed occasionally when lines are entered and readline() returns, rather than once per second. Reproduced on ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.6.0] and ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin10.8.0]. The RubyInline gem allows a workaround: require 'inline' class BetterReadline inline :C do |builder| builder.include '' builder.include '' src = <