Aeron
- MAeron
- JIRAUSER625244
- Asia/Tokyo
- Yes
- No
MCL-17399
Started a few weeks ago, coinciding with the release of Minecraft Launcher version 2.2.2162 on macOS, the launcher will open as expected and launch Minecraft as expected. However, even though the Launcher window will close, it will sometimes remain in memory while the game is running (launcher is set to close after opening Minecraft) and after Minecraft has been properly quit. It goes unnoticed until I attempt to run the launcher again and it will not open because there is already an instance in memory that is now labeled as "(Not Responding)" by Activity Monitor. The process must be force quit through the Activity Monitor app to allow it to open again. Only then will it will run as expected and load Minecraft as expected.
This does not happen every time, but most of the time. When I watch the Launcher's process in Activity Monitor, it closes like it's suppose to.My computer does not go to sleep and it does not seem to be tied to how long Minecraft is played. It just randomly, and frequently, remains in memory and ultimately stops working, requiring user intervention to allow the Launcher to be used again.If it matters, macOS itself does not register this as a crash (Apple's crash report prompt never opens in response to this behavior)
Started a few weeks ago, coinciding with the release of Minecraft Launcher version 2.2.2162 on macOS, the launcher will open as expected and launch Minecraft as expected. However, even though the Launcher window will close, it will sometimes remain in memory while the game is running (launcher is set to close after opening Minecraft) and after Minecraft has been properly quit. It goes unnoticed until I attempt to run the launcher again and it will not open because there is already an instance in memory that is now labeled as "(Not Responding)" by Activity Monitor. The process must be force quit through the Activity Monitor app to allow it to open again. Only then will it will run as expected and load Minecraft as expected.
This does not happen every time, but most of the time.
When I watch the Launcher's process in Activity Monitor, it closes like it's suppose to.I caught it in the act, the process "Minecraft Launcher" stays open in the Activity Monitor and is running without issue while playing Minecraft. A short moment after Minecraft is quit, the launcher becomes unresponsive (see attached screenshot).My computer does not go to sleep and it does not seem to be tied to how long Minecraft is played. It just randomly, and frequently, remains in memory and ultimately stops working, requiring user intervention to allow the Launcher to be used again.
If it matters, macOS itself does not register this as a crash (Apple's crash report prompt never opens in response to this behavior)
Launcher does not quit and becomes unresponsive afterlaunching game in macOS MojaveLauncher process does not quit and becomes unresponsive after closing game in macOS Mojave
macOS Mojave (10.14
.6) and macOSBig Sur, running on 64-bit hardware.Both the OS and the Launcher are the most recent version.macOS Mojave (10.14), Catalina (10.15), and Big Sur (11), running on 64-bit hardware. Most recent release of the Launcher and all respective OSes.
WorkaroundVery often, this issue can be fixed by quitting or force quitting the Minecraft Launcher process in the Activity Monitor. To attempt this temporary fix:
- Open the spotlight by pressing Command (⌘) and Space at the same time
- Search for "Activity Monitor", and when you see its name, click it to open it
- On the top of the application window, select the "Energy" tab
- Find Minecraft Launcher in the list of applications, making use of the search bar in the top right of the application if necessary
- Double-click the Minecraft Launcher, and a properties window should appear
- Click the "Quit" button in the bottom left of the properties window
- Select "Force Quit"
After you've completed these steps, you should be able to close the Activity Monitor, and reopen the Minecraft Launcher.
Started a few weeks ago, coinciding with the release of Minecraft Launcher version 2.2.2162 on macOS, the launcher will open as expected and launch Minecraft as expected. However, even though the Launcher window will close, it will sometimes remain in memory while the game is running (launcher is set to close after opening Minecraft) and after Minecraft has been properly quit. It goes unnoticed until I attempt to run the launcher again and it will not open because there is already an instance in memory that is now labeled as "(Not Responding)" by Activity Monitor. The process must be force quit through the Activity Monitor app to allow it to open again. Only then will it will run as expected and load Minecraft as expected.
This does not happen every time, but most of the time.
When I watch the Launcher's process in Activity Monitor, it closes like it's suppose to.I caught it in the act, the process "Minecraft Launcher" stays open in the Activity Monitor and is running without issue while playing Minecraft. A short moment after Minecraft is quit, the launcher becomes unresponsive (see attached screenshot).My computer does not go to sleep and it does not seem to be tied to how long Minecraft is played. It just randomly, and frequently, remains in memory and ultimately stops working, requiring user intervention to allow the Launcher to be used again.
If it matters, macOS itself does not register this as a crash (Apple's crash report prompt never opens in response to this behavior)
Add 2021/7/7: Since this bug has persisted for so long (How long does Mojang typically let a reliable crash-related bug exist?), I've learned a few other things about it.
Every time the Minecraft client receives an update by pressing the Play button, in a situation where a new version is allowed to be downloaded before the game is launched, this somehow allows the launcher to properly close and will (in my experience so far) always launch normally the next time it is used. After that, however, it will return to its previously broken behavior of failing to close itself gracefully.
I also discovered that the bug doesn't require launching Minecraft at all to take effect. I accidentally left the launcher open for about an hour and this resulted in the launcher still being usable (you can navigate within the app and interact with links) except for the Play button for Minecraft. This probably also applied for the Play button for Minecraft Dungeons as well. Pressing Play after leaving the launcher open for an extended period of time makes the text change to three dots as a loading animation for a few seconds then back to Play without actually doing anything. Going into Activity Monitor shows that the launcher is in fact no longer responding and must be force quit.
WorkaroundVery often, this issue can be fixed by quitting or force quitting the Minecraft Launcher process in the Activity Monitor. To attempt this temporary fix:
- Open the spotlight by pressing Command (⌘) and Space at the same time
- Search for "Activity Monitor", and when you see its name, click it to open it
- On the top of the application window, select the "Energy" tab
- Find Minecraft Launcher in the list of applications, making use of the search bar in the top right of the application if necessary
- Double-click the Minecraft Launcher, and a properties window should appear
- Click the "Quit" button in the bottom left of the properties window
- Select "Force Quit"
After you've completed these steps, you should be able to close the Activity Monitor, and reopen the Minecraft Launcher.
Started a few weeks ago, coinciding with the release of Minecraft Launcher version 2.2.2162 on macOS, the launcher will open as expected and launch Minecraft as expected. However, even though the Launcher window will close, it will sometimes remain in memory while the game is running (launcher is set to close after opening Minecraft) and after Minecraft has been properly quit. It goes unnoticed until I attempt to run the launcher again and it will not open because there is already an instance in memory that is now labeled as "(Not Responding)" by Activity Monitor. The process must be force quit through the Activity Monitor app to allow it to open again. Only then will it will run as expected and load Minecraft as expected.
This does not happen every time, but most of the time.
When I watch the Launcher's process in Activity Monitor, it closes like it's suppose to.I caught it in the act, the process "Minecraft Launcher" stays open in the Activity Monitor and is running without issue while playing Minecraft. A short moment after Minecraft is quit, the launcher becomes unresponsive (see attached screenshot).My computer does not go to sleep and it does not seem to be tied to how long Minecraft is played. It just randomly, and frequently, remains in memory and ultimately stops working, requiring user intervention to allow the Launcher to be used again.
If it matters, macOS itself does not register this as a crash (Apple's crash report prompt never opens in response to this behavior)
Add 2021/7/7: Since this bug has persisted for so long (How long does Mojang typically let a reliable crash-related bug exist?), I've learned a few other things about it.
Every time the Minecraft client receives an update by pressing the Play button, in a situation where a new version is allowed to be downloaded before the game is launched, this somehow allows the launcher to properly close and will (in my experience so far) always launch normally the next time it is used. After that, however, it will return to its previously broken behavior of failing to close itself gracefully.
I also discovered that the bug doesn't require launching Minecraft at all to take effect. I accidentally left the launcher open for about an hour and this resulted in the launcher still being usable (you can navigate within the app and interact with links) except for the Play button for Minecraft. This probably also applied for the Play button for Minecraft Dungeons as well. Pressing Play after leaving the launcher open for an extended period of time makes the text change to three dots as a loading animation for a few seconds then back to Play without actually doing anything. Going into Activity Monitor shows that the launcher is in fact no longer responding and must be force quit.
WorkaroundVery often, this issue can be fixed by quitting or force quitting the Minecraft Launcher process in the Activity Monitor. To attempt this temporary fix:
- Open the spotlight by pressing Command (⌘) and Space at the same time
- Search for "Activity Monitor", and when you see its name, click it to open it
- On the top of the application window, select the "Energy" tab
- Find Minecraft Launcher in the list of applications, making use of the search bar in the top right of the application if necessary
- Double-click the Minecraft Launcher, and a properties window should appear
- Click the "Quit" button in the bottom left of the properties window
- Select "Force Quit"
After you've completed these steps, you should be able to close the Activity Monitor, and reopen the Minecraft Launcher.
Started a few weeks ago, coinciding with the release of Minecraft Launcher version 2.2.2162 on macOS, the launcher will open as expected and launch Minecraft as expected. However, even though the Launcher window will close, it will sometimes remain in memory while the game is running (launcher is set to close after opening Minecraft) and after Minecraft has been properly quit. It goes unnoticed until I attempt to run the launcher again and it will not open because there is already an instance in memory that is now labeled as "(Not Responding)" by Activity Monitor. The process must be force quit through the Activity Monitor app to allow it to open again. Only then will it will run as expected and load Minecraft as expected.
This does not happen every time, but most of the time.
When I watch the Launcher's process in Activity Monitor, it closes like it's suppose to.I caught it in the act, the process "Minecraft Launcher" stays open in the Activity Monitor and is running without issue while playing Minecraft. A short moment after Minecraft is quit, the launcher becomes unresponsive (see attached screenshot).My computer does not go to sleep and it does not seem to be tied to how long Minecraft is played. It just randomly, and frequently, remains in memory and ultimately stops working, requiring user intervention to allow the Launcher to be used again.
If it matters, macOS itself does not register this as a crash (Apple's crash report prompt never opens in response to this behavior)
Add 2021/7/7: Since this bug has persisted for so long (How long does Mojang typically let a reliable crash-related bug exist?), I've learned a few other things about it.
Every time the Minecraft client receives an update by pressing the Play button, in a situation where a new version is allowed to be downloaded before the game is launched, this somehow allows the launcher to properly close and will (in my experience so far) always launch normally the next time it is used. After that, however, it will return to its previously broken behavior of failing to close itself gracefully.
I also discovered that the bug doesn't require launching Minecraft at all to take effect. I accidentally left the launcher open for about an hour and this resulted in the launcher still being usable (you can navigate within the app and interact with links) except for the Play button for Minecraft.
This probably also applied for the Play button for Minecraft Dungeons as well.Pressing Play after leaving the launcher open for an extended period of time makes the text change to three dots as a loading animation for a few seconds then back to Play without actually doing anything. Going into Activity Monitor shows that the launcher is in fact no longer responding and must be force quit.
The launcher's log? Where is that located?
With the release of Minecraft 1.17, the problem was temporarily relieved. I was able to run the launcher several times in a row without resorting to manually killing it first. I briefly thought that Java 8 was somehow the catalyst for this bug. However, after a couple of days, it returned to the previous behavior of needing to be manually closed through Activity Monitor almost every single time. (Minecraft Java Edition 1.17, running Java 16 64-bit)
I added the current release of the launcher available on Mojave to the list of affected versions.
I have not had this issue since the release of Launcher 2.2.3964, can anyone else confirm?