General

Profile

MiiJaySung (Jason Earl)

  • Login: MiiJaySung
  • Email: jason@hybd.net
  • Registered on: 01/27/2010
  • Last sign in: 05/05/2011

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 0 0

Activity

05/05/2011

02:04 AM Ruby Bug #4608: Ctrl-c to interrupt script causes hang and 100% cpu's core load
I filed a similar bug on Rail's lighthouse a few days ago too. I've found Natty in fact to be pretty bad in some areas regarding stablity, I really hope the Ubuntu team clean up the various issues soon (So anyone reading this, I suggest ... MiiJaySung (Jason Earl)

01/30/2010

06:40 PM Ruby Bug #1392: Object#extend leaks memory on Ruby 1.9.1
=begin
Thanks for the quick patch. It certainly seems to do the trick.
=end
MiiJaySung (Jason Earl)

01/28/2010

05:46 PM Ruby Bug #1392: Object#extend leaks memory on Ruby 1.9.1
=begin
My trunk build is: ruby 1.9.2dev (2010-01-27 trunk 26434) [x86_64-linux]

Your clone code above doesn't leak either for me.

However both of these simplified scenarios leak:

./ruby -e 'loop { Class.new.__send__ :include, ...
MiiJaySung (Jason Earl)

01/27/2010

07:14 AM Ruby Bug #1392: Object#extend leaks memory on Ruby 1.9.1
=begin
And just to confirm, using an indefinite loop like Roger points out makes my Ruby process grow continuously. After about 6-8 minutes my Ruby process had grown to 12% of memory usage and showed no sign of going down.
=end
MiiJaySung (Jason Earl)
06:58 AM Ruby Bug #1392: Object#extend leaks memory on Ruby 1.9.1
=begin
I've just tried the code above with Ruby 1.9.2 Preview 1 and the current trunk.

I can confirm that this doing

./ruby leak_test.rb LEAK

on the above versions appears to leak memory as ps aux / top reports a 0.8% m...
MiiJaySung (Jason Earl)

Also available in: Atom