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?
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.
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.
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 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!
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?
The launcher is asking a server somewhere what version is the newest and downloading the files if there's a change. The whole process for updating that is probably automated, unlike packaging a .deb for download, so it's not surprising that the download is out of date and self-updates as soon as it runs.
I think the launcher and the auth servers are speaking different languages. I think maybe either the thing the launcher uses to interpret data from the server, or the thing the launcher uses to encode and send data to the server, is borked, and the server is just sending back the 403 as its way of going "What is this garbage? I don't even know what it means" when the launcher sends it gibberish.
Workaround for now: use a third-party launcher. Another user and I were able to get the vanilla launcher to start, but it isn't communicating correctly with Mojang's authentication servers. (Issue MCL-22271 if you're curious.)
I've been using PolyMC, which you can get right off the Mint 19 Software Manager. It works great. There are others, and they tend to have good wikis and/or YouTube videos to explain how to set them up. It takes a few minutes, but it's probably way easier than upgrading your entire OS version.
It seems the devs are assuming that, because these versions of Linux are long-term support, glibc and/or its parent library is backwards-compatible. For whatever reason, distro maintainers do not want the update installed on older systems. No idea why. But I remembered that I actually had this issue with glibc/libc6 earlier this year. A modding tool for Baldur's Gate: Enhanced Edition used the updated library version and I got it to work by downloading the tool's source code and compiling it on my own machine. (I'm a Linux n00b, so it was an adventure.) If that incident would be helpful to whoever's working on this problem, I can track down the related forum posts.
Attempted to update via apt. It said there was an update, but it seems to be installing the same version again.
michelle@Minty:~$ sudo apt reinstall minecraft-launcher
The following packages will be REINSTALLED:
minecraft-launcher
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/52.3 MB of archives. After unpacking 0 B will be used.
(Reading database ... 390789 files and directories currently installed.)
Preparing to unpack .../minecraft-launcher_2.1.9618_amd64.deb ...
Unpacking minecraft-launcher (2.1.9618) over (2.1.9618) ...
Setting up minecraft-launcher (2.1.9618) ...
Processing triggers for desktop-file-utils (0.23+linuxmint8) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Uninstalled the launcher and tried the .deb. It gives its version as 1.1.26. Still having the same issue. I'm attaching my bootstrap-log (which I think is the installation log?) and launcher-log, which is still complaining about glibc 2.29.
I'm not sure whatever version is on the package repo is completely up-to-date, because it seems like this is an earlier version than the one available in this tracker. 2.1.9618 vs. 2.3.377. When I get the launcher to start, it always says there's an update available and links to the minecraft.net download page for Linux, even though that's an older version.
Edit: Okay, the update manager had an update for minecraft-launcher. This time, the launcher opened without me having to reinstall dependencies as I did before, but it's still not able to authorize a login and it's still version 2.1.9618.
I've been playing this game since 2011, first on Windows and now on Linux, and this is the first time I've ever had an issue with the launcher. That's pretty remarkable reliability for any kind of software. I'm guessing the issue came up from the process of getting the existing launcher to play nice with Microsoft's fancy-dancy login system across three platforms, which must have been quite a process. Hiccups are understandable.
Thanks to the team who sorted this out. I hope you guys get paid many emeralds.
Crystal Soulslayer
MC-78787
MCL-22271
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?
I was directed here by Mustek from this thread:
MC-78787It 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.
Okay, thanks.
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.
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 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!
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?
Thanks! c:
The launcher is asking a server somewhere what version is the newest and downloading the files if there's a change. The whole process for updating that is probably automated, unlike packaging a .deb for download, so it's not surprising that the download is out of date and self-updates as soon as it runs.
I think the launcher and the auth servers are speaking different languages. I think maybe either the thing the launcher uses to interpret data from the server, or the thing the launcher uses to encode and send data to the server, is borked, and the server is just sending back the 403 as its way of going "What is this garbage? I don't even know what it means" when the launcher sends it gibberish.
Yep, PolyMC works. Thanks!
Workaround for now: use a third-party launcher. Another user and I were able to get the vanilla launcher to start, but it isn't communicating correctly with Mojang's authentication servers. (Issue
MCL-22271if you're curious.)I've been using PolyMC, which you can get right off the Mint 19 Software Manager. It works great. There are others, and they tend to have good wikis and/or YouTube videos to explain how to set them up. It takes a few minutes, but it's probably way easier than upgrading your entire OS version.
It seems the devs are assuming that, because these versions of Linux are long-term support, glibc and/or its parent library is backwards-compatible. For whatever reason, distro maintainers do not want the update installed on older systems. No idea why. But I remembered that I actually had this issue with glibc/libc6 earlier this year. A modding tool for Baldur's Gate: Enhanced Edition used the updated library version and I got it to work by downloading the tool's source code and compiling it on my own machine. (I'm a Linux n00b, so it was an adventure.) If that incident would be helpful to whoever's working on this problem, I can track down the related forum posts.
Attempted to update via apt. It said there was an update, but it seems to be installing the same version again.
Uninstalled the launcher and tried the .deb. It gives its version as 1.1.26. Still having the same issue. I'm attaching my bootstrap-log (which I think is the installation log?) and launcher-log, which is still complaining about glibc 2.29.
I'm not sure whatever version is on the package repo is completely up-to-date, because it seems like this is an earlier version than the one available in this tracker. 2.1.9618 vs. 2.3.377. When I get the launcher to start, it always says there's an update available and links to the minecraft.net download page for Linux, even though that's an older version.
Edit: Okay, the update manager had an update for minecraft-launcher. This time, the launcher opened without me having to reinstall dependencies as I did before, but it's still not able to authorize a login and it's still version 2.1.9618.
I've been playing this game since 2011, first on Windows and now on Linux, and this is the first time I've ever had an issue with the launcher. That's pretty remarkable reliability for any kind of software. I'm guessing the issue came up from the process of getting the existing launcher to play nice with Microsoft's fancy-dancy login system across three platforms, which must have been quite a process. Hiccups are understandable.
Thanks to the team who sorted this out. I hope you guys get paid many emeralds.
Uninstall the launcher, download the .deb from the website, and let it auto-update. Worked for me.