Unsure if related to MC-5520, as error is reported differently
I got a similar error (not exact but same problem, could not fullscreen, which forced the game to crash upon loading since Fullscreen was the default) after my nVidia Driver updated for my 550ti. I was finally able to fix it by going into the nVidia settings and changing Scaling to Full-Screen instead of Aspect Ratio under "Adjust Desktop Size and Resolution". The Hertz was already at 60 by default. This was a temporary fix, however, as the game soon crashed with an "Out of Memory" error within about 5 minutes of gameplay.
I actually got several intermittent errors before fullscreen stopped completely. The sound would not play at all about 50% of the time. I reinstalled Minecraft as a result, which for some reason changed the default JVM arguments to "-Xmx1G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M" instead of the previous -"Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M". So, after I had fixed the video settings, I had to change my JVM arguments back (Actually bumped it a little to "-Xmx3G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn256M" after I confirmed it fixed the "Out of Memory issue"). Running with absolutely no issues now. I will note: I installed Minecraft with the onboard graphics the first time; installed the 550ti at a later time, so Minecraft may be applying the wrong arguments based on my system configuration.
I should note that I will now have to fix the JVM arguments with each time there is a Minecraft update,* as the JVM arguments still default to the previously defunct arguments with each new version I install, no matter the version* even if I go back to 1.6 or enable experimental snapshots into 1.13. It even applied the arguments to Optifine when I attempted to install after reinstalling Minecraft. Had I not kept a backup of the arguments for reference, I would have been completely at a loss.
[EDIT] The issue seems to be the launcher applying a new JVM Argument that is not compatible with the nVidia drivers by default. Since I usually change them to use more resources, I did not have any issues since the release of the new launcher until I performed the reinstall. The other issue with the sound also started with the new launcher, but likely a compatibility issue with my GPU as well, since my sound is handled through HDCP, but I was able to play before the reinstall.
Attachments
Comments 5
Your crashes don't appear to be related to MC-5520 since neither of them have similar crash reports. They also show two different crashes all-together. That being said, seeing as you're experiencing this issue when going into fullscreen, have you tried in the latest snapshot (currently 17w48a)? This one updates the game libraries and MC-5520 (amongst others) are reported as fixed with it. If you still experience crashes there, please attach the resulting reports here.
The attached logs and crash reports are from the outdated 1.12. Please attach files from the development snapshot 17w48a or later.
Solution has resolved the issue. 17w47a and 17w47b both were crashing as well, but once I went with 17w48a, there seems to be no issues with any versions, previous or current.
I need to add: Although the solution did fix the crashing, Minecraft is now taxing my GPU heavily and now it sounds like a jet engine while playing.
17w49b
[media]
1.12 with new default arguments
1.12 with old arguments
1.12.2 with new default arguments
I'll submit as new issue, as the actual issue is different.
Nevermind, I may have found the issue. If not, I'll resubmit.
Okay, yeah. The default framerate is set to "Unlimited" now, when it used to default to "VSYNC"
Please do not mark unreleased versions as affected.
You don't have access to them yet.