Misc #3757
closedGC bug after loading gem
Description
=begin
This bug is very general. All you have to do is:
- require enough of the stdlib
- require some gem
- GC.stress=true
- create a few objects
See the attached gcbug.rb.
The bug appears on both x86_64-linux and i686-linux.
It does not happen with ruby-1.9.2, AFAICT.
It does happen with both p302 and p299 of ruby-1.8.7.
The bug is typically reported as one of the following:
gcbug.rb:24: [BUG] Segmentation fault
ruby 1.8.7 (2010-08-16 patchlevel 302) [x86_64-linux]
gcbug.rb:24: [BUG] rb_gc_mark(): unknown data type 0x18(0x1bbaf00) non object
ruby 1.8.7 (2010-08-16 patchlevel 302) [x86_64-linux]
=end
Files
Updated by rogerdpack (Roger Pack) over 13 years ago
=begin
does this occur with 1.9.3dev?
-r
=end
Updated by rogerdpack (Roger Pack) over 13 years ago
=begin
Is there any reason to believe it will occur with 1.9.3dev?
It might. I ran into an odd gc bug once with 1.9.3dev and not 1.9.2 (I think it's gone, but just checking out of curiosity..).
Thanks.
=end
Updated by jeremyevans0 (Jeremy Evans) over 4 years ago
- Description updated (diff)
- Status changed from Open to Closed