[MCL-3437] IllegalArgumentException when launcher tries to start game

When opening the launcher, it seemed to run rather slow and then when it tried to launch the game, it stopped appearing to do anything, leaving the launcher log and the game log tabs both blank. Upon running the game through the terminal, it was found to be an IllegalArgumentException preventing the game from launching.
I am somewhat uncertain about the steps to reproduce, but I started from a clean install of Minecraft, without any data files to provide as detailed of a log as I could. Through guidance at the IRC support, I've gone through many attempts to fix it, but the same bug has still persisted. Feel free to ask anything you need to about the environment, I'll answer asap.

Attachments

Console Error Log.txt

Comments 4

CubeTheThird 2015-02-10T05:15:59Z

Note:

java.lang.IllegalArgumentException
at com.google.gson.internal.$Gson$Preconditions.checkArgument($Gson$Preconditions.java:42) ~[Minecraft.jar:?]
at com.google.gson.GsonBuilder.registerTypeAdapter(GsonBuilder.java:448) ~[Minecraft.jar:?]
at net.minecraft.launcher.game.MinecraftGameRunner.getMinecraftArguments(MinecraftGameRunner.java:285) ~[launcher.jar:1.6.11]
at net.minecraft.launcher.game.MinecraftGameRunner.launchGame(MinecraftGameRunner.java:177) ~[launcher.jar:1.6.11]
at com.mojang.launcher.game.runner.AbstractGameRunner.onDownloadJobFinished(AbstractGameRunner.java:186) [launcher.jar:1.6.11]
at com.mojang.launcher.updater.download.DownloadJob.popAndDownload(DownloadJob.java:122) [launcher.jar:1.6.11]
at com.mojang.launcher.updater.download.DownloadJob.access$000(DownloadJob.java:12) [launcher.jar:1.6.11]
at com.mojang.launcher.updater.download.DownloadJob$1.run(DownloadJob.java:86) [launcher.jar:1.6.11]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [?:1.7.0_75]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_75]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_75]
at java.lang.Thread.run(Thread.java:745) [?:1.7.0_75]

Sam Dixon 2015-02-11T17:38:32Z

Update: I figured out what was going on. It was trying to use an extension that I had for plugin development. Deleting the extension from the java extensions folder fixed it, although I would ask if there is some way to force it to ignore that.
Otherwise, feel free to close it (Facepalms)

CubeTheThird 2015-02-11T19:51:25Z

Glad to hear this was solved. I'm wondering if this extension added something to the java path, or a JVM argument or something like that.

Sam Dixon 2015-02-12T00:12:39Z

It was actually from having craftbukkit in the extensions folder so that I didn't have to load it in to each workspace manually, so what I think happened is that it tried to launch the craftbukkit file.