ruby-core

Mailing list archive

[#33640] [Ruby 1.9-Bug#4136][Open] Enumerable#reject should not inherit the receiver's instance variables — Hiro Asari <redmine@...>

Bug #4136: Enumerable#reject should not inherit the receiver's instance variables

10 messages 2010/12/08

[#33667] [Ruby 1.9-Bug#4149][Open] Documentation submission: syslog standard library — mathew murphy <redmine@...>

Bug #4149: Documentation submission: syslog standard library

11 messages 2010/12/10

[#33683] [feature:trunk] Enumerable#categorize — Tanaka Akira <akr@...>

Hi.

14 messages 2010/12/12
[#33684] Re: [feature:trunk] Enumerable#categorize — "Martin J. Dst" <duerst@...> 2010/12/12

[#33687] Towards a standardized AST for Ruby code — Magnus Holm <judofyr@...>

Hey folks,

23 messages 2010/12/12
[#33688] Re: Towards a standardized AST for Ruby code — Charles Oliver Nutter <headius@...> 2010/12/12

On Sun, Dec 12, 2010 at 9:55 AM, Magnus Holm <judofyr@gmail.com> wrote:

[#33689] Re: Towards a standardized AST for Ruby code — "Haase, Konstantin" <Konstantin.Haase@...> 2010/12/12

On Dec 12, 2010, at 17:46 , Charles Oliver Nutter wrote:

[#33763] [Ruby 1.9-Bug#4168][Open] WeakRef is unsafe to use in Ruby 1.9 — Brian Durand <redmine@...>

Bug #4168: WeakRef is unsafe to use in Ruby 1.9

43 messages 2010/12/17

[#33815] trunk warnflags build issue with curb 0.7.9? — Jon <jon.forums@...>

As this may turn out to be a 3rd party issue rather than a bug, I'd like some feedback.

11 messages 2010/12/22

[#33833] Ruby 1.9.2 is going to be released — "Yuki Sonoda (Yugui)" <yugui@...>

-----BEGIN PGP SIGNED MESSAGE-----

15 messages 2010/12/23

[#33846] [Ruby 1.9-Feature#4197][Open] Improvement of the benchmark library — Benoit Daloze <redmine@...>

Feature #4197: Improvement of the benchmark library

15 messages 2010/12/23

[#33910] [Ruby 1.9-Feature#4211][Open] Converting the Ruby and C API documentation to YARD syntax — Loren Segal <redmine@...>

Feature #4211: Converting the Ruby and C API documentation to YARD syntax

10 messages 2010/12/26

[#33923] [Ruby 1.9-Bug#4214][Open] Fiddle::WINDOWS == false on Windows — Jon Forums <redmine@...>

Bug #4214: Fiddle::WINDOWS =3D=3D false on Windows

15 messages 2010/12/27

[ruby-core:33796] [Ruby 1.8-Bug#4181][Open] Backport Ruby 1.9 singleton.rb, since 1.8's is not thread-safe

From: Charles Nutter <redmine@...>
Date: 2010-12-21 15:04:42 UTC
List: ruby-core #33796
Bug #4181: Backport Ruby 1.9 singleton.rb, since 1.8's is not thread-safe
http://redmine.ruby-lang.org/issues/show/4181

Author: Charles Nutter
Status: Open, Priority: Immediate
ruby -v: Any Ruby 1.8 version

Ruby 1.9 modified singleton.rb by eliminating much of the lazy init logic, using a real mutex instead of Thread.critical, and eliminating the redefinition of "instance" on first call. None of these changes have been backported into a 1.8 release, which means all 1.8 releases have a broken singleton.rb.

The following script breaks under any version of 1.8:

<code>
 require 'singleton'
 $jruby = RUBY_PLATFORM =~ /java/
 require 'jruby/synchronized' if $jruby
 
 loop do
   $inits = []
   $inits.extend JRuby::Synchronized if $jruby
   classes = []
   1000.times do
     classes << Class.new do
       include Singleton
     end
   end
   
   (0..10).map do
     Thread.new do
       classes.each do |cls|
         cls.instance
       end
     end
   end.map(&:join)
   puts "loop completed"
 end
</code>

Results:

~/projects/jruby ➔ ruby -v singleton_killer.rb 
ruby 1.8.7 (2010-08-16 patchlevel 302) [i686-darwin10.4.0]
loop completed
loop completed
loop completed
loop completed
loop completed
loop completed
loop completed
loop completed
loop completed
singleton_killer.rb:18: undefined method `instance' for #<Class:0x1001896a0> (NoMethodError)
	from singleton_killer.rb:1:in `join'
	from singleton_killer.rb:1:in `to_proc'
	from singleton_killer.rb:21:in `map'
	from singleton_killer.rb:21
	from singleton_killer.rb:5:in `loop'
	from singleton_killer.rb:5


~/projects/jruby ➔ ruby -v singleton_killer.rb 
ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]
loop completed
loop completed
loop completed
loop completed
singleton_killer.rb:18: undefined method `instance' for #<Class:0x100348c70> (NoMethodError)
	from singleton_killer.rb:1:in `join'
	from singleton_killer.rb:1:in `to_proc'
	from singleton_killer.rb:21:in `map'
	from singleton_killer.rb:21
	from singleton_killer.rb:5:in `loop'
	from singleton_killer.rb:5

This can lead to lazy failures in any library that uses singleton.rb. See also this commit to Nokogiri, where they had to stop using Singleton because of this issue:

https://github.com/tenderlove/nokogiri/commit/5eb036e39ea85a8e12eebee11bc5086b0e4ce6e3


----------------------------------------
http://redmine.ruby-lang.org

In This Thread

Prev Next