Project

General

Profile

Backport #3597

Memory leak in 1.9.1

Added by rkh (Konstantin Haase) about 9 years ago. Updated 7 days ago.

Status:
Closed
Priority:
Normal
[ruby-core:31426]

Description

=begin
The following code produces a memory leak, but only on 1.9.1 (p429), but neither on 1.9.2 (rc2) nor on 1.8.7 (p299):

 ruby -e 'loop { Object.new.extend Module.new; GC.start }'

Konstantin
=end

History

#1

Updated by nobu (Nobuyoshi Nakada) about 9 years ago

  • Category set to core
  • Status changed from Open to Assigned
  • Assignee set to yugui (Yuki Sonoda)

=begin

=end

#2

Updated by tenderlovemaking (Aaron Patterson) almost 9 years ago

=begin
On Thu, Jul 22, 2010 at 06:12:32AM +0900, Konstantin Haase wrote:

Bug #3597: Memory leak in 1.9.1
http://redmine.ruby-lang.org/issues/show/3597

Author: Konstantin Haase
Status: Open, Priority: Normal
ruby -v: ruby 1.9.1p429 (2010-07-02 revision 28523) [i386-darwin10.4.0]

The following code produces a memory leak, but only on 1.9.1 (p429), but neither on 1.9.2 (rc2) nor on 1.8.7 (p299):

ruby -e 'loop { Object.new.extend Module.new; GC.start }'

If this doesn't produce a memory leak on 1.9.2 rc2 and 1.8.7 p299, is
this really a bug?

--
Aaron Patterson
http://tenderlovemaking.com/

Attachment: (unnamed)
=end

#3

Updated by rkh (Konstantin Haase) almost 9 years ago

=begin

On Jul 23, 2010, at 09:06 , Aaron Patterson wrote:

If this doesn't produce a memory leak on 1.9.2 rc2 and 1.8.7 p299, is
this really a bug?

If 1.9.1 is still supported and there is going to be another patch level, then I sure think so.

Konstantin

=end

#4

Updated by jeremyevans0 (Jeremy Evans) 7 days ago

  • Status changed from Assigned to Closed
  • Description updated (diff)

Also available in: Atom PDF