Setting MaxPermSize=384m makes noise during every startup on Java 8 #79

Closed
copumpkin opened this Issue Jul 18, 2014 · 4 comments

Comments

Projects
None yet
4 participants
@copumpkin

Using JVM 8, I (not unexpectedly) get:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384m; support was removed in 8.0

during startup. Perhaps that setting should be conditional on JVM version, since it's irrelevant as of 8?

@paulp

This comment has been minimized.

Show comment Hide comment
@paulp

paulp Jul 18, 2014

Owner

Patches welcome. I already tried and the challenge exceeded my interest.

Owner

paulp commented Jul 18, 2014

Patches welcome. I already tried and the challenge exceeded my interest.

@dwijnand

This comment has been minimized.

Show comment Hide comment
@dwijnand

dwijnand Jul 19, 2014

Collaborator

I've got a fix, but the bats/stubs tests are failing and I've no idea how to solve it, after a couple of hours..

See: https://github.com/dwijnand/sbt-extras/commits/no-more-max-perm-size-notice-spam

Collaborator

dwijnand commented Jul 19, 2014

I've got a fix, but the bats/stubs tests are failing and I've no idea how to solve it, after a couple of hours..

See: https://github.com/dwijnand/sbt-extras/commits/no-more-max-perm-size-notice-spam

@paulp

This comment has been minimized.

Show comment Hide comment
@paulp

paulp Jul 19, 2014

Owner

Indeed that's exactly how it went for me.

commit 4d6385693e
Author: Paul Phillips <paulp@improving.org>
Date:   3 months ago

Dropped -MaxPermSize=384m and -Dfile.encoding=UTF8.

On java8 the first generates a warning every time the jvm
is started and I'm pretty sure the latter is unnecessary
now that apple is no longer foisting macro-macro-man on us.

I tried to only drop those options on java8 and leave java7
and previous alone, but some interaction I don't understand
meant the tests would not pass. Contributions welcome on
that point. You can always enumerate the options you want
so it's an inconvenience at worst.

...

commit f8ea9c1474
Author: Paul Phillips <paulp@improving.org>
Date:   2 months ago

Restore -XX:MaxPermSize.

Looks like I'll live with the warning on java8, because
sbt is unusable without this option on java7.
Owner

paulp commented Jul 19, 2014

Indeed that's exactly how it went for me.

commit 4d6385693e
Author: Paul Phillips <paulp@improving.org>
Date:   3 months ago

Dropped -MaxPermSize=384m and -Dfile.encoding=UTF8.

On java8 the first generates a warning every time the jvm
is started and I'm pretty sure the latter is unnecessary
now that apple is no longer foisting macro-macro-man on us.

I tried to only drop those options on java8 and leave java7
and previous alone, but some interaction I don't understand
meant the tests would not pass. Contributions welcome on
that point. You can always enumerate the options you want
so it's an inconvenience at worst.

...

commit f8ea9c1474
Author: Paul Phillips <paulp@improving.org>
Date:   2 months ago

Restore -XX:MaxPermSize.

Looks like I'll live with the warning on java8, because
sbt is unusable without this option on java7.
@sphonicmachines

This comment has been minimized.

Show comment Hide comment
@sphonicmachines

sphonicmachines Jul 19, 2014

If you doable g1gc in Java 8 this should force to use old style GC which means the option is valid? Don't think we need g1gc for sbt?

Sent from my iPhone

On 19 Jul 2014, at 14:27, Paul Phillips notifications@github.com wrote:

Indeed that's exactly how it went for me.

commit 4d63856
Author: Paul Phillips paulp@improving.org
Date: 3 months ago

Dropped -MaxPermSize=384m and -Dfile.encoding=UTF8.

On java8 the first generates a warning every time the jvm
is started and I'm pretty sure the latter is unnecessary
now that apple is no longer foisting macro-macro-man on us.

I tried to only drop those options on java8 and leave java7
and previous alone, but some interaction I don't understand
meant the tests would not pass. Contributions welcome on
that point. You can always enumerate the options you want
so it's an inconvenience at worst.

...

commit f8ea9c1
Author: Paul Phillips paulp@improving.org
Date: 2 months ago

Restore -XX:MaxPermSize.

Looks like I'll live with the warning on java8, because
sbt is unusable without this option on java7.

Reply to this email directly or view it on GitHub.

If you doable g1gc in Java 8 this should force to use old style GC which means the option is valid? Don't think we need g1gc for sbt?

Sent from my iPhone

On 19 Jul 2014, at 14:27, Paul Phillips notifications@github.com wrote:

Indeed that's exactly how it went for me.

commit 4d63856
Author: Paul Phillips paulp@improving.org
Date: 3 months ago

Dropped -MaxPermSize=384m and -Dfile.encoding=UTF8.

On java8 the first generates a warning every time the jvm
is started and I'm pretty sure the latter is unnecessary
now that apple is no longer foisting macro-macro-man on us.

I tried to only drop those options on java8 and leave java7
and previous alone, but some interaction I don't understand
meant the tests would not pass. Contributions welcome on
that point. You can always enumerate the options you want
so it's an inconvenience at worst.

...

commit f8ea9c1
Author: Paul Phillips paulp@improving.org
Date: 2 months ago

Restore -XX:MaxPermSize.

Looks like I'll live with the warning on java8, because
sbt is unusable without this option on java7.

Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment