Project

General

Profile

Actions

Bug #16900

closed

Disposable call-cache introduced memory leak

Added by jeremyevans0 (Jeremy Evans) almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Target version:
-
[ruby-core:98445]

Description

b9007b6c548f91e88fd3f2ffa23de740431fa969 (Introduce disposable call-cache) introduced a memory leak for classes that include or prepend modules. Taking the example memory leak script used in the commit message for 5922c954614e5947a548780bb3b894626affe6dd:

    module M; def bar; end; end
    loop{
      Class.new do
        def foo; end
        prepend M
      end
    }

There is unbounded growth:

jeremy   56984  0.0  0.1 59540 14940 p2  S+      5:15PM    0:00.19 ruby example.rb
jeremy   56984  0.0  0.1 61852 18640 p2  S+      5:15PM    0:00.40 ruby example.rb
jeremy   56984  0.0  0.1 62700 19940 p2  S+      5:15PM    0:00.62 ruby example.rb
jeremy   56984  0.0  0.1 63696 21364 p2  S+      5:15PM    0:00.83 ruby example.rb
jeremy   56984  4.1  0.1 64632 22748 p2  S+      5:15PM    0:01.05 ruby example.rb
jeremy   56984  4.1  0.1 65664 24188 p2  S+      5:15PM    0:01.26 ruby example.rb
jeremy   56984  4.1  0.2 66632 25432 p2  S+      5:15PM    0:01.47 ruby example.rb
jeremy   56984  4.1  0.2 67484 26552 p2  S+      5:15PM    0:01.70 ruby example.rb
jeremy   56984  8.5  0.2 68456 27772 p2  S+      5:15PM    0:01.92 ruby example.rb
jeremy   56984  8.5  0.2 69536 29164 p2  S+      5:15PM    0:02.14 ruby example.rb
jeremy   56984  8.5  0.2 70424 30252 p2  S+      5:15PM    0:02.36 ruby example.rb

This issue appears to be limited to classes that include or prepend modules.

  • Same memory leak when switching from prepend to include
  • No memory leak when switching from Class.new to Module.new
  • No memory leak when removing the prepend
  • No memory leak when removing the prepend and subclassing the class.
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0