Backport #461
closedRe: Hard question: Any ideas why this code leaks memory?
Description
=begin
Hi,
At Wed, 20 Aug 2008 04:46:24 +0900,
Sven C. Koehler wrote in [ruby-talk:311847]:
could someone help me understand why this code leaks memory? (I am using
ruby 1.8.6 (2007-12-03 patchlevel 113) [x86_64-linux].)def rss_leaks
/^VmRSS:\s+(\d+)/m.match(File.open("/proc/#{$$}/status") {|f|
f.read })[1].to_i
end
Calling GC.start inbetween does not help, but when we rewrote rss_leaks
this way the leaks disappeared:def rss_no_leaks()
d = File.open("/proc/#{$$}/status") {|f| f.read }
/^VmRSS:\s+(\d+)/m.match(d)[1].to_i
end
Seems a bug.
--
Nobu Nakada
=end
Updated by rogerdpack (Roger Pack) about 16 years ago
=begin
You should try SVN HEAD and see if it's still there.
See also http://rubyforge.org/tracker/?func=detail&atid=1698&aid=15425&group_id=426
=end
Updated by shyouhei (Shyouhei Urabe) almost 16 years ago
- Assignee set to matz (Yukihiro Matsumoto)
=begin
=end
Updated by shyouhei (Shyouhei Urabe) over 14 years ago
- Status changed from Open to Assigned
- ruby -v set to -
=begin
=end
Updated by shyouhei (Shyouhei Urabe) about 14 years ago
- Category set to core
- Status changed from Assigned to Feedback
=begin
Can this still happen? I can't observe on my machine with
ruby 1.8.8dev (2010-09-24 revision 27061) [x86_64-linux].
irb(main):005:0> 100000.times { rss_leaks }; rss_leaks
=> 5616
irb(main):006:0> 100000.times { rss_leaks }; rss_leaks
=> 5616
irb(main):007:0> 100000.times { rss_leaks }; rss_leaks
=> 5616
irb(main):008:0> 100000.times { rss_leaks }; rss_leaks
=> 5616
=end
Updated by jeremyevans0 (Jeremy Evans) over 5 years ago
- Tracker changed from Bug to Backport
- Project changed from Ruby 1.8 to Backport187
- Description updated (diff)
- Status changed from Feedback to Closed
- ruby -v deleted (
-)