MCL-2444Changing profile runs on Event Dispatch Thread
Changing profile on the launcher runs on the Event Dispatch Thread, which means if you change to a profile that is logged into another Minecraft account, the launcher temporarily freezes whilst it contacts the authentication servers.
Any task that could take time shouldn't run on the EDT.
What I expected to happen was...:
The launcher would work much like it does when you first start it: there is a 'Play Offline' button until it logs into your account, and the launcher works normally, with interaction possible.
What actually happened was...:
The launcher froze whilst it was attempting to login to the other account, with no interaction available.
Steps to Reproduce:
1. Have 2 profiles on the launcher, both logged into 2 separate Minecraft/Mojang accounts.
2. Switch from one profile to the other.
3. The launcher will temporarily freeze whilst it logs into the other account.
Notes:
Especially apparent when authentication servers are down, where it freezes whilst it tries (and fails) to contact the servers.
Environment
Windows 7 Professional SP1 64-bit
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
Created Issue:
Changing profile runs on Event Dispatch Thread
Changing profile on the launcher runs on the Event Dispatch Thread, which means if you change to a profile that is logged into another Minecraft account, the launcher temporarily freezes whilst it contacts the authentication servers.
Any task that could take time shouldn't run on the EDT.What I expected to happen was...:
The launcher would work much like it does when you first start it: there is a 'Play Offline' button until it logs into your account, and the launcher works normally, with interaction possible.What actually happened was...:
The launcher froze whilst it was attempting to login to the other account, with no interaction available.Steps to Reproduce:
1. Have 2 profiles on the launcher, both logged into 2 separate Minecraft/Mojang accounts.
2. Switch from one profile to the other.
3. The launcher will temporarily freeze whilst it logs into the other account.Notes:
Especially apparent when authentication servers are down, where it freezes whilst it tries (and fails) to contact the servers.Environment
Windows 7 Professional SP1 64-bit
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
Changing profile on the launcher runs on the Event Dispatch Thread, which means if you change to a profile that is logged into another Minecraft account, the launcher temporarily freezes whilst it contacts the authentication servers.
Any task that could take time shouldn't run on the EDT.What I expected to happen was...:
The launcher would work much like it does when you first start it: there is a 'Play Offline' button until it logs into your account, and the launcher works normally, with interaction possible.What actually happened was...:
The launcher froze whilst it was attempting to login to the other account, with no interaction available.Steps to Reproduce:
1. Have 2 profiles on the launcher, both logged into 2 separate Minecraft/Mojang accounts.
2. Switch from one profile to the other.
3. The launcher will temporarily freeze whilst it logs into the other account.Notes:
Especially apparent when authentication servers are down, where it freezes whilst it tries (and fails) to contact the servers.
relates to
Windows 7 Professional SP1 64-bit
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)Windows 7 Professional SP1 64-bit
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
Confirmed.
Is this still a concern in the current Minecraft Launcher version 2.0.805 / 2.0.806? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. It will be reopened it as soon as the requested information has been delivered.
This issue does not affect 2.0.806.