Ruby Issue Tracking System

03/14/2010

01:00 PM Backport187 Backport #2597: Crash in p248 while installing gem

=begin
Can confirm the segmentation faults using "ruby-1.8.7-p248". No segmentation faults using "ruby-1.8.7-p174". ... igal (Igal Koshevoy)

01/08/2009

01:32 PM Ruby 1.8 Bug #990 (Closed): YAML::load segfaults

=begin
The Syck-based YAML implementation shipped with Ruby can produce invalid output that it itself cannot parse o... igal (Igal Koshevoy)

07/06/2008

02:22 AM Ruby 1.8 Bug #216: Memory leaks in 1.8.6p230 and p238

=begin
Good news, I think the memory leak problem is fixed.

I've applied Matz's re.c patch to my copy of p265 (... igal (Igal Koshevoy)

07/05/2008

08:56 AM Ruby 1.8 Bug #216: Memory leaks in 1.8.6p230 and p238

=begin
Rolando Abarca,

Excellent work, your sample code clearly demonstrates the memory leak and narrows its lo... igal (Igal Koshevoy)

07/03/2008

11:51 PM Ruby 1.8 Bug #216: Memory leaks in 1.8.6p230 and p238

=begin
Rolando Abarca: No, my test merely proves that a memory leak exists, but doesn't identify where. If you or so... igal (Igal Koshevoy)

07:32 AM Ruby 1.8 Bug #216 (Closed): Memory leaks in 1.8.6p230 and p238

=begin
WARNING: Do not use Ruby 1.8.6 releases p230 through p238 in production! There are bugs in the Ruby interpret... igal (Igal Koshevoy)

03:31 AM Ruby 1.8 Bug #199: Possible patches for critical segfaults and vulnerabilities available for review in ruby-talk

=begin
I've re-run the test suites, along with some additional ones, against Ruby 1.8.6 SVN 17631 and the results se... igal (Igal Koshevoy)

06/28/2008

09:27 PM Ruby 1.8 Bug #199: Possible patches for critical segfaults and vulnerabilities available for review in ruby-talk

=begin
Urabe Shyouhei wrote:
> Sorry for a late reply but I think I've fixed this issue. Can someone
> please t... igal (Igal Koshevoy)