mojira.dev
MCL-17151

Launcher crashes on modded profile start

After the latest beta update the launcher crashes when trying to start certain custom profiles. (See attached) The profile(s) works in stable (2.2.1862)

Unfortunately I'm unable to find any kind of updated log for the launcher. If that gets created and is necessary then please point me into its direction.

EDIT: The error seems to only occur when trying to start the game in certain (previously used) Minecraft game directories, not in others getting me to believe that something in this old directory is not liked by the launcher update?

Attachments

Comments 8

Hi Phoenix, please report this to the Fabric developers. We are not the developers of this mod so we can't fix the issue.

Can you please provide me with some info where (crash) logs for the launcher are stored? Or what changes were made in the launcher which would prevent the profile in question from starting? (Because it worked just fine in 2.2.1862 so something in the launcher must've changed)

You should be able to find the logs in your logs folder.

@Justin Drennan I'm talking about the Launcher log, not the game. The launcher does not generate logs there.

@Ined can you please provide the requested information, it's impossible to debug this (and the dll doesn't contain debug information). Just as a note: The profile is a valid one which worked before and the launcher shouldn't crash if a startup error or invalid profile occurs? Seeing as this is now in stable this bug should become a way higher priority... I don't get how this even made it out of the test version.

Opened an issue with fabric anyways but I still believe that the launcher should handle whatever error occurs there more gracefully.

Someone over at fabric pointed out to me where the launcher log was stored, somehow I missed that. Attached it to the issue.

Hey @unknown, I might actually have closed this bug prematurely. Would you mind checking that the versions we have available as beta is working for you? You can enable this by going to Settings, ticking the box, and restarting the Launcher.

Yes, the new beta solves this. Sorry for not including the launcher log and information about the custom java installation in the original issue.

Phoenix616

(Unassigned)

Unconfirmed

Retrieved