Crystal Soulslayer

Thanks! c:

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?

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!

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.

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.

Okay, thanks.

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.

Hi there. I should have clarified--it has happened in modded Minecraft, but it also happens in vanilla on a fresh installation with no mods anywhere near it, and even to the launcher itself. Do I still need to create a new ticket?