You used to be able to supply a server and port for minecraft to connect to upon startup. now that crashes.

What I expected to happen was...:
You can provide launch arguments --server and --port to have minecraft connect to the specified server instead of showing the main menu.

What actually happened was...:
A crash, see the crash report. Note that the server still says <name> joined the game before the crash.

Steps to Reproduce:
1. Create a new profile (by copying the 1.14.2 one, and renaming the folder as well as changing the "id")
2. Add arguments "-server", "localhost", "-port", "25565" to the game args
3. Start a local 1.14.2 server
4. Run the game
5. have a crash producing the attached report

Speculation as to what may be the issue:
1.14 introduced the new deffered loading and loading screen which is actually an overlay while the actual main GUI (mostly the main menu screen) already has it's init method called. Supplying --server and --port makes the actual screen the server connect screen, causing the client to connect to a server and then try to render the world before all the rendering stuff has been initialized (because the loading screen still is overlaid and the data is still asyncly being prepared)

Note that there is not supposed to be striken-through text here but Jira formatting makes this very hard to not have.
crash-2019-06-15_03.16.37-client.txt is 1.14.2
crash-2019-06-15_02.53.00-client.txt is 1.14.3-pre3