[MC-77103] New "Provided" JVM very unstable

MC is much laggier using your version of MC. Running the old MC, with a 64-bit 1.7 JVM makes MC a lot faster.

With the new JVM, MC seems to need to allocate a lot of memory, doing a full cleanup cycle every 3 seconds or so, making a huge lag spike (the Memory jumps up and down quickly). Every now and then MC crashes (once in an hour or so, see the JVM crash report attached.

Oh, and I have UAC completely disabled, doesn't fix it.

Attachments

Comments 16

kumasasa 2015-01-31T11:25:36Z

Please attach the complete output of the "Launcher Log" which can be found on the second tab of the launcher.

If the launcher closes after game start, please edit your profile and select "Launcher visibility" then, "Keep the launcher open".

Rubisk 2015-01-31T19:17:29Z

http://pastebin.com/24ZJ53DV

Important stuff is at the end, I had to restart the game a few times doing some tests so there's some junk at the top.

Rubisk 2015-02-04T18:30:20Z

Added a clean Luancher Log and Game output file, hope it helps.

Rubisk 2015-02-11T20:45:08Z

I've done some research myself, doesn't look like it's a line of code causing the crash. The instructions it crashes at seem to be completely different most of the time...

Added some more JVM logs, so you can see that it's not the same everytime.

Crystal Soulslayer 2015-03-17T22:31:21Z

I was directed here by Mustek from this thread: MC-78787

It does seem to be the same issue, right down to the "5120" at the end of the problematic frame line. I notice we're using processors in the same family--you have the Q8300, I have the Q8400. Uh-oh.

6 more comments

Rubisk 2015-03-18T22:03:27Z

I'll try get a complete core dump this weekend, maybe that will clear some stuff up (probably won't, unfortunately).

Crystal Soulslayer 2015-03-19T00:58:10Z

I'm just worried we're about to discover another Intel processor incompatibility, like the one known to affect some of the mobile CPUs with integrated graphics. This old beast is six years old, but I couldn't afford a thumb drive at the moment. I don't want to lose Minecraft in addition to all my triple-A titles. :c

Anyway, I'm not noticing any significant lag on my end. There was a little stuttering, but I lowered my mipmap levels and view distance, and there's no significant performance loss now, despite that I am using the prepackaged Java 8. I have noticed that, unsurprisingly, the crashes happen much more frequently the more intensive the task; starting up Minecraft and creating a new world are almost always crashing my game.

Rubisk 2015-04-27T09:56:54Z

So, after 40 hours+ of research, I came to the conclusion that the deprecated Incremental CMS garbage-collector is causing this issue.

I'm not a java expert, but I would recommend Mojang to disable this by default in the JVM arguments section. Normal CMS garbage-collection is still required, but the incremental version seems to crash some processors (at least mine).

I'll drop a link down to the documentation for CMS garbage-collectors for more information.
http://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/cms.html

(quick fix: Remove -XX:+CMSIncrementalMode out of your JVM arguments in the Edit Profile section. Make sure to keep -XX:+UseConcMarkSweepGC in there or your FPS will drop drastically.

Rubisk 2015-04-27T10:06:49Z

I also found MC-69351. That issue is different from mine, since that one is caused by broken graphics drivers, and this is a crash within a JVM core process/source code issue. (look at the difference in the Problematic frame)

Crystal Soulslayer 2015-04-27T20:43:56Z

I had already removed the -XX:+CMSIncrementalMode line, as I routinely add/change the startup arguments to allocate more RAM and so on. I tried putting it back in, to no avail. Still the same sporadic crashes with the same four digits at the end of the problematic frame.

Is there something specific in a log that leads you to the conclusion that the incremental CMS argument is the one directly responsible? I've noticed the crashes seem to happen in clusters--sometimes I can't get it started at all, then I'll come back a half hour later and it runs fine. This may be a major contributor to the fact that, prior to starting a support thread, I thought I'd fixed this crash about ninety times. Makes me wonder if the timing isn't coincidence on your machine, as well.

Rubisk 2015-04-27T21:31:10Z

There was some error complaining about incremental CMS being deprecated and most likely removed soon, so I took it out (after figuring out what it actualy was). No crashes ever since (3 days). Took quite a while to figure out how to disable it without cutting my FPS down to 10% of normal.

Crystal Soulslayer 2015-04-27T22:49:27Z

I took it out for the same reason when I saw that error in a crash log, but it had no apparent affect on my FPS, and I'm still crashing regardless of whether it's enabled or not. I also get access violations from time to time just trying to run the launcher itself or even the .jar version of the Forge installer, which is making me wonder if my system is having a problem with Java itself. If yours has been resolved just with that argument removed, that would seem to suggest that we have separate issues. Glad yours has apparently been resolved, though. There is hope!

Crystal Soulslayer 2015-05-05T06:04:05Z

It's definitely a more generalized Java issue, as things other than Minecraft, even Java-based browser games, are crashing with the exact same kind of error. Is there somewhere I can go where highly Java-literate people can figure out what's going on if I ask nicely?

kumasasa 2015-05-05T06:24:16Z

You might try Minecraft help chat (best with a reference to this ticket) and/or if you're sure that's a bug, report it here: http://bugreport.java.com/

Crystal Soulslayer 2015-05-05T06:28:50Z

Thanks! c:

[Mod] Neko 2016-10-20T22:52:52Z

Is this still an issue in the most recent versions (i.e. 1.10.2, or 16w42a) of Minecraft?