RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 786229 - segfault in garbage collection
Summary: segfault in garbage collection
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ruby
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vít Ondruch
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 734713 dc-ruby-segfault 786231 786238 789120
TreeView+ depends on / blocked
 
Reported: 2012-01-31 18:50 UTC by Jim Meyering
Modified: 2013-03-13 20:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 786231 786238 (view as bug list)
Environment:
Last Closed: 2012-04-03 11:09:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jim Meyering 2012-01-31 18:50:32 UTC 
Description of problem: ruby segfaults in garbage collection
In deltacloud development, we've been plagued by the exact same 
problem documented here:

http://bugs.ruby-lang.org/issues/4339

Version-Release number of selected component (if applicable): ruby-1.8.7.299-6.el6


How reproducible: every time


Steps to Reproduce:
1. run the reproducer from the above URL:
   http://bugs.ruby-lang.org/attachments/1446/REPRO4.rb
2.
3.
  
Actual results: segfault


Expected results: no segfault
 

Additional info:
Comment 2 Jim Meyering 2012-01-31 18:53:56 UTC 
ps, I built ruby-1.8.7.352-3 but with that added patch[0],
and confirmed that the segfault we'd been getting every time
via deltacloudd is no longer appearing.

[0] http://bugs.ruby-lang.org/attachments/2243/ruby-1.8.7-marshal.patch
Comment 3 Vít Ondruch 2012-02-01 07:40:27 UTC 
Jim, could you please do me a favor and report the same into the upstream bug? You see that I had no response from upstream for some while, so may be other voice can change it. I don't like to apply this patch directly, because as you see, the previous version which appeared to work correctly was leaking, so I'd like some review from upstream.
Comment 4 Jim Meyering 2012-02-01 08:25:43 UTC 
(In reply to comment #3)
> Jim, could you please do me a favor and report the same into the upstream bug?
> You see that I had no response from upstream for some while, so may be other
...

Yes, I noticed that.  It's been 3 months.  I suspect that 1.8.7 is low priority for them.  I've added this note:

http://bugs.ruby-lang.org/issues/4339#note-13
Comment 5 Vít Ondruch 2012-02-01 08:43:16 UTC 
Thank you. I appreciate that.
Comment 7 Suzanne Logcher 2012-02-14 23:29:57 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 8 Vít Ondruch 2012-04-03 10:57:04 UTC 
Hi Jim, 

The patch was released in 6.2.z to resolve rhbz#799959. Can we close this issue now?
Comment 9 Jim Meyering 2012-04-03 11:05:54 UTC 
Hi Vit,
Sure, that's fine with me.
Note You need to log in before you can comment on or make changes to this bug.