[jruby-dev] [jira] (JRUBY-7129) Joining a thread that died from a Java error does not kill the parent thread

[Chris Rogers (JIRA)]

Chris Rogers created JRUBY-7129 Joining a thread that died from a Java error does not kill the parent thread Issue Type: Bug Affects Versions: JRuby 1.7.3 Assignee: Unassigned Components: Java Integration Created: 21/Mar/13 12:13 PM Description: Joining a thread that died from a normal Ruby error will kill the parent thread, as expected. The "should not be here" text is never printed: $ jruby -e "Thread.new{raise 'error'}.join; puts 'should not be here'" RuntimeError: error (root) at -e:1 However, if the thread died from a raw Java error, joining the thread only prints a trace, and the "should not be here" text is printed. rcrog...@proc1-ss1.dev:~/statsheet$ jruby -e "Thread.new{a = []; loop{a << 'word'}}.join; puts 'should not be here'" Exception in thread "RubyThread-1: -e:1" java.lang.OutOfMemoryError: Java heap space at org.jruby.RubyString.newStringShared(RubyString.java:571) [...] at org.jruby.internal.runtime.RubyRunnable.run(RubyRunnable.java:98) at java.lang.Thread.run(Thread.java:679) should not be here Environment: Ubuntu Project: JRuby Priority: Major Reporter: Chris Rogers

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email