https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112013-01-14T01:00:12ZRuby Issue Tracking SystemRuby master - Bug #7648: GServer does not close cleanly from signal interrupt contexthttps://bugs.ruby-lang.org/issues/7648?journal_id=353842013-01-14T01:00:12Zjleo3 (Joe Leo)joseph.leo3@gmail.com
<ul></ul><p>Confirming that this is still an issue on RC1:</p>
<p>ruby -v<br>
ruby 2.0.0dev (2013-01-07 trunk 38733) [i686-linux]</p>
<p>/home/joe/lib/lib/ruby/2.0.0/gserver.rb:116:in <code>synchronize': can't be called from trap context (ThreadError) from /home/joe/lib/lib/ruby/2.0.0/gserver.rb:116:in </code>stop'<br>
from /home/joe/dev/bane/lib/bane/launcher.rb:19:in <code>block in stop' from /home/joe/dev/bane/lib/bane/launcher.rb:19:in </code>each'<br>
from /home/joe/dev/bane/lib/bane/launcher.rb:19:in <code>stop' from ./bin/bane:22:in </code>block in '<br>
from /home/joe/lib/lib/ruby/2.0.0/gserver.rb:140:in <code>call' from /home/joe/lib/lib/ruby/2.0.0/gserver.rb:140:in </code>join'<br>
from /home/joe/lib/lib/ruby/2.0.0/gserver.rb:140:in <code>join' from /home/joe/dev/bane/lib/bane/launcher.rb:15:in </code>block in join'<br>
from /home/joe/dev/bane/lib/bane/launcher.rb:15:in <code>each' from /home/joe/dev/bane/lib/bane/launcher.rb:15:in </code>join'<br>
from ./bin/bane:23:in `'</p> Ruby master - Bug #7648: GServer does not close cleanly from signal interrupt contexthttps://bugs.ruby-lang.org/issues/7648?journal_id=356022013-01-25T12:16:04Zko1 (Koichi Sasada)
<ul><li><strong>Category</strong> set to <i>lib</i></li><li><strong>Target version</strong> set to <i>2.0.0</i></li></ul><p>Who can check it?</p> Ruby master - Bug #7648: GServer does not close cleanly from signal interrupt contexthttps://bugs.ruby-lang.org/issues/7648?journal_id=363612013-02-17T13:51:26Zko1 (Koichi Sasada)
<ul><li><strong>Assignee</strong> set to <i>mame (Yusuke Endoh)</i></li></ul><p>No response here.</p> Ruby master - Bug #7648: GServer does not close cleanly from signal interrupt contexthttps://bugs.ruby-lang.org/issues/7648?journal_id=363902013-02-17T14:45:21Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Target version</strong> changed from <i>2.0.0</i> to <i>2.6</i></li></ul> Ruby master - Bug #7648: GServer does not close cleanly from signal interrupt contexthttps://bugs.ruby-lang.org/issues/7648?journal_id=395742013-05-31T13:17:20Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> changed from <i>mame (Yusuke Endoh)</i> to <i>kosaki (Motohiro KOSAKI)</i></li></ul><p>kosaki-san, what do you think?</p>
<p>--<br>
Yusuke Endoh <a href="mailto:mame@tsg.ne.jp" class="email">mame@tsg.ne.jp</a></p> Ruby master - Bug #7648: GServer does not close cleanly from signal interrupt contexthttps://bugs.ruby-lang.org/issues/7648?journal_id=414372013-08-31T02:20:36Zkosaki (Motohiro KOSAKI)kosaki.motohiro@gmail.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Rejected</i></li></ul><p>Holding mutex in trap is deadlockable. It is what ruby complained. The best workaround is to make new thread in trap handler and stop gserver asynchnorously, I think.</p>