[MC-121285] Crash on start when resolution is changed in profile

When setting the resolution for the snapshot profile the game fails to start and only shows the "Game Crash" message.

From the launcher_log.txt:

[1025/174005:INFO:GameCallbacks.cpp(178)] launcher/launcher (main) info Exception in thread "main" joptsimple.OptionArgumentConversionException: Cannot parse argument '--height' of option width
	at joptsimple.AbstractOptionSpec.convertWith(AbstractOptionSpec.java:92)
	at joptsimple.ArgumentAcceptingOptionSpec.convert(ArgumentAcceptingOptionSpec.java:277)
	at joptsimple.OptionSet.valuesOf(OptionSet.java:223)
	at joptsimple.OptionSet.valueOf(OptionSet.java:172)
	at net.minecraft.client.main.Main.main(SourceFile:90)
Caused by: joptsimple.internal.ReflectionException: java.lang.NumberFormatException: For input string: "--height"
	at joptsimple.internal.Reflection.reflectionException(Reflection.java:136)
	at joptsimple.internal.Reflection.invoke(Reflection.java:118)
	at joptsimple.internal.MethodInvokingValueConverter.convert(MethodInvokingValueConverter.java:48)
	at joptsimple.internal.Reflection.convertWith(Reflection.java:124)
	at joptsimple.AbstractOptionSpec.convertWith(AbstractOptionSpec.java:90)
	... 4 more
Caused by: java.lang.NumberFormatException: For input string: "--height"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:580)
	at java.lang.Integer.valueOf(Integer.java:766)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:483)
	at joptsimple.internal.Reflection.invoke(Reflection.java:116)
	... 7 more

Linked issues

is duplicated by 41

MC-8400 Redstone block and piston not updating Resolved

MC-8604 in some computers can't play LAN worlds no appear the LAN world or appear the error connection timed out Resolved

MC-8949 Map Enlaging BUGs Resolved

MC-8955 Comparators not causing updates Resolved

MC-8988 Allocated memory is different than Total available in F3 Menu. Resolved

36 more links

Attachments

2017-10-26 11-58-09.flv

2017-12-11 17-31-08.mp4

launcher_log.txt

launcher_log-custom-profile-snapshot-crash.txt

Comments 34

EchoBlade 2017-10-26T19:43:03Z

Confirmed for 17w43b.

Christian Francis Core 2017-10-26T21:03:01Z

I think thats whats happening to me as well, I hope they can fix this infuriating bug....

I also had this happen on 17w43a just so you guys know.

Ely G 2017-10-26T21:36:29Z

can confirm for both 17w43a and 17w43b

FaRo1 2017-10-26T21:53:56Z

Can you people please look at the affected versions? You have now written four redundant confirmations.
Here's a video showing that the launcher launches another launcher when it is set to be kept open when starting the game: https://www.youtube.com/watch?v=s6H6Fx_ZG9w

Christian Francis Core 2017-10-26T22:04:45Z

Fabian what do you want us to do, I tried both versions and no luck, and besides we were just trying to let you guys know.

Edit: Ok, sorry if I was across as rude, I am just stressed out by this whole thing....

24 more comments

Meri Diana 2017-10-26T22:24:13Z

Quite at the top of the page it tells you "Affects Version/s" where you could theoretically have seen that the versions you guys confirmed as affected were already known/inserted. Fabian just wanted to let you all know where to look the next time so you don't have to unnecessarily confirm. The thing is that everyone who watches bugposts will get an email notification whenever someone writes anything or even just edits their comment. Which means it can get a bit annoying if several people comment or edit unnecessarily 🙂

Just keep an eye in the future on the "Affects Version/s", but really thank you for trying to help 🙂

(PS: In case you or anyone else seeing this bugpost, not knowing how you can run your launcher as long this bug is not fixed:
Start your client, go to "Launch options", click the Snapshot profile, then simply disable the "Resolution" slider like so: https://puu.sh/y7XLD/0582f4d747.png)

Christian Francis Core 2017-10-26T22:29:33Z

Ok, thanks Meri and again Im sorry guys, i was just stressed I think Ill ty it.

Oh it works thanks.

EchoBlade 2017-11-08T16:12:20Z

Confirmed for 17w45a.

Kevin Sullivan 2017-11-08T19:26:48Z

I too can confirm with Sebastian Cila above, that this still happens on version 17w45a if 'Resolution' is switched ON in launch settings, but if switched off - game will run fine

Ely G 2017-11-10T20:25:20Z

confirmed for 17w45b. this is an extremely frustrating one not to fix.

EchoBlade 2017-11-15T21:22:09Z

Confirmed for 17w46a.

Phoenix616 2017-11-22T14:25:59Z

Confirmed for 17w47a

SunCat 2017-11-23T00:38:44Z

@unknown, you don't have to comment when you can update the affected versions yourself

Ely G 2017-11-28T00:40:01Z

confirmed for 17w48a

Ely G 2017-12-06T22:23:58Z

confirmed for 17w49a

Ely G 2017-12-07T19:23:14Z

confirmed for 17w49b

enemysfriend22 2017-12-11T16:33:09Z

confirmed for 17w50a

Sander Hõbelaid 2017-12-12T17:42:57Z

Turning off the resulation does not work for me. It just crashes. Log also does not save.

FaRo1 2017-12-12T17:49:08Z

Then you have a different problem. Try turning on log output.

Muizz Siddique 2017-12-20T01:34:24Z

When booting up the game with the "Resolution" switch on, without even changing the resolution, the launcher gives a pop up saying "Game Crash - An unexpected issue..." while leaving an empty "latest.log". This is on 17w50a.

Edit: I would give the info from "launcher_log.txt" file but it is 14MB. ~~Edit 2: I deleted it and reproduced the crash and was only left with 564KB. Too big for pastebin, what do I do?~~ Edit 3: I added the log file to the ticket.

BratrilliantGamer7 2018-01-30T07:58:02Z

confirmed for 18w03b

Bailey Hosner 2018-02-15T16:42:46Z

Confirmed for snapshot 18w07b. Same problem.

TopStiGear 2018-02-17T00:05:59Z

Crashing with 18w07c too

RAM 2018-02-23T16:26:08Z

And 18w08b

Kalorii 2018-03-02T18:20:55Z

Persisting for 18w09a. Can launch without any resolution args but can't customise resolution without it crashing back to the launcher. Zero output or indication as to why this is. Please fix this as it's been an issue throughout and I'd like to play these snapshots.

Kalorii 2018-03-06T17:00:44Z

18w10a also does this. I've uploaded my launcher log to see if it will shed some light on this. There are errors being shown in there that aren't shown as actual errors when viewing the output via the launcher.

Bailey Hosner 2018-04-10T17:10:48Z

Same issue persists, snapshot 18w14b.

JochCool 2018-04-11T19:09:23Z

Still an issue in 18w15a 😞

RAM 2018-04-21T05:18:54Z

Abd 18w16a

RAM 2018-05-08T13:37:36Z

Snapshot 18w19a
MacOS 10.13.4 (17E202)
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

Enabling resolution no longer crashes, but it does not use the resolution settings (1708x960). Game is still 854x480.

Meri Diana 2018-05-08T13:50:57Z

I can confirm this is the case, and no crashes.

[media]

I also tested by completely closing everything and restarting after saving the changes, but it still gets launched with the default resolution, as you can see above.

Ely G 2018-05-08T14:41:31Z

It seems to work correctly in the updated launcher (2.0.1049)

Meri Diana 2018-05-08T14:53:53Z

Confirmed, I've just received the new launcher update, I've been in the 1033 version before, in 18w19a.
All good, thank you 🙂

RAM 2018-05-08T18:46:42Z

Confirmed. Launcher did not update earlier, even on restart. Now on 2.0.1051, all better. Thanks.