librelist archives

« back to archive

Follow-up

Follow-up

From:
Kc Erb
Date:
2013-12-16 @ 22:44
Hi all,

I just wanted to follow up on the memory eater app. I finally figured out
how to strip it down to the most basic thing that will sit and eat memory.

I'm putting it to the mailing list to play with because I'm not sure if
this is a bug or expected behavior.

Have fun: https://gist.github.com/KCErb/7995751


-KC


 "If there is an exception to every rule, then every rule must have at
least one exception; the exception to this one being that it has no
exception."

Re: [shoes] Follow-up

From:
James Gifford
Date:
2013-12-16 @ 23:15
Interesting. I'm impressed.

I see if you can do that with normal C or Jruby too. I think you can...
On Dec 16, 2013 5:45 PM, "KC Erb" <iamkcerb@gmail.com> wrote:

> Hi all,
>
> I just wanted to follow up on the memory eater app. I finally figured out
> how to strip it down to the most basic thing that will sit and eat memory.
>
> I'm putting it to the mailing list to play with because I'm not sure if
> this is a bug or expected behavior.
>
> Have fun: https://gist.github.com/KCErb/7995751
>
>
> -KC
>
>
>  "If there is an exception to every rule, then every rule must have at
> least one exception; the exception to this one being that it has no
> exception."
>

Re: [shoes] Follow-up

From:
Kc Erb
Date:
2013-12-16 @ 23:54
By the way, I just updated the gist because you don't need to call the
buggy code 1000 times to create this error. It seems that just calling an
image a few times with a do block is all that's needed to eat memory.


On Mon, Dec 16, 2013 at 4:15 PM, James Gifford <james@jamesrgifford.com>wrote:

> Interesting. I'm impressed.
>
> I see if you can do that with normal C or Jruby too. I think you can...
> On Dec 16, 2013 5:45 PM, "KC Erb" <iamkcerb@gmail.com> wrote:
>
>> Hi all,
>>
>> I just wanted to follow up on the memory eater app. I finally figured out
>> how to strip it down to the most basic thing that will sit and eat memory.
>>
>> I'm putting it to the mailing list to play with because I'm not sure if
>> this is a bug or expected behavior.
>>
>> Have fun: https://gist.github.com/KCErb/7995751
>>
>>
>> -KC
>>
>>
>>  "If there is an exception to every rule, then every rule must have at
>> least one exception; the exception to this one being that it has no
>> exception."
>>
>


-- 
 "If there is an exception to every rule, then every rule must have at
least one exception; the exception to this one being that it has no
exception."

Re: [shoes] Follow-up

From:
Eric Watson
Date:
2013-12-17 @ 06:35
On Dec 16, 2013, at 4:44 PM, KC Erb <iamkcerb@gmail.com> wrote:

> I just wanted to follow up on the memory eater app. I finally figured 
out how to strip it down to the most basic thing that will sit and eat 
memory.

This doesn’t exactly sit and eat memory on my machine ;)

  dingo:shoes4 eric$ bin/shoes ~/tmp/memory-leak.rb
  Error: Your application used more memory than the safety cap of 500M.
  Specify -J-Xmx####m to increase it (#### = cap size in MB).
  Specify -w for full OutOfMemoryError stack trace

Thanks a lot for pointing out this bug!

Re: [shoes] Follow-up

From:
Tobias Pfeiffer
Date:
2013-12-17 @ 10:26
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi everyone,

I created this issue: https://github.com/shoes/shoes4/issues/504

Thanks a lot KC - narrowing down a bug in an application to a small
reproducible script is one heck of a job. Thanks for this - now we can
look forward to fixing it thanks to you!

I added it to the rc1 milestone for now, if someone feels like it
should be fixed before alpha please feel free to change it! :-)

Cheers,
Tobi

On Tue 17 Dec 2013 07:35:06 AM CET, Eric Watson wrote:
>
> On Dec 16, 2013, at 4:44 PM, KC Erb <iamkcerb@gmail.com> wrote:
>
>> I just wanted to follow up on the memory eater app. I finally figured 
out how to strip it down to the most basic thing that will sit and eat 
memory.
>
> This doesn’t exactly sit and eat memory on my machine ;)
>
>   dingo:shoes4 eric$ bin/shoes ~/tmp/memory-leak.rb
>   Error: Your application used more memory than the safety cap of 500M.
>   Specify -J-Xmx####m to increase it (#### = cap size in MB).
>   Specify -w for full OutOfMemoryError stack trace
>
> Thanks a lot for pointing out this bug!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSsCbWAAoJEBzX32BGBaITOFEH/RUEfujtBjFazTE02fO512KY
GwWyny5/695ouUpfTzeIK401CIfJYj85TTl1wccG/IoR+SKRj4gbqc3F1crr4+Ap
6IWcoaHFvxEtdRAC4nAKZGRAZO4mBPerea6hnlSmzPnoAfGyB4e1CncOUBJBMuTD
mmfRsD/EZJRVnCBdvVUCUHdMuutLUVPT4EtvkvBAt34MC+ZGhVtTSOcmNhx50ZqY
Hu0mIZyjcxN0O4XxOFfA/Oj/GlQ/hu16j7FnAaXcwm7p/KfbUwqiPzdjSHFKHpom
YZwbjIW9r3BnqOMGt06g2Q62Slob2H7tZdLS2YUHbwddLNTRYXV6csjh15v9coo=
=FnVZ
-----END PGP SIGNATURE-----