I am not sure, but it seemed like "something" bad floated into jdk8 for a little while, and then floated back out again. I haven't kept close enough track of the gc-dev mailing list, but for a few days I was frequently running out of memory when I had not been before (i.e., doing a build, or simply initializing some of the internal tests) -- this on a machine where when I checked, at least 4G was free for the taking.
Something happened, and the problems went away. On 2013-09-13, at 6:59 PM, Charles Oliver Nutter <head...@headius.com> wrote: > On Sat, Sep 14, 2013 at 12:57 AM, Charles Oliver Nutter > <head...@headius.com> wrote: >> * More memory required when running with indy versus without, all >> other things kept constant (reproduced by two people, one of them me) > > I should say *significantly more* memory here. The app Alex was > running had to go from 1GB heap / 256MB permgen to 2G/512M when it was > running *fine* before...and this is just for running the *tests*. > > - Charlie > _______________________________________________ > mlvm-dev mailing list > mlvm-dev@openjdk.java.net > http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
