Launcher process does not quit and becomes unresponsive after closing game in macOS
Very 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.
Environment
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.
Linked Issues
is duplicated by12
MC-226256Game processes don't exit and prevent relaunch on macOSDuplicate
MCL-17341Launcher Won't openDuplicateMCL-17563Launcher HangsDuplicateMCL-17581Minecraft Launcher doesn't fully quit when playing snapshots on a Mac with the M1 chipDuplicateMCL-17719Launcher won't open DuplicateMCL-17749Launcher doesn't launch (MacOS)DuplicateMCL-18070wont open on mac two timesDuplicateMCL-18120Launcher not respondingDuplicateMCL-18398Minecraft launcher stops responding on MacOSDuplicateMCL-18568Minecraft Launcher requires computer restart to openDuplicateMCL-18716Launcher doesn't quit properly on Mac OS X, workaround force quit in activity monitor to restartDuplicateMCL-19210Minecraft Launcher stays open in macOS Activity Monitor after launchingDuplicate
Created Issue:
Launcher does not quit and becomes unresponsive after launching game in macOS Mojave
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)
Environment
macOS Mojave (10.14.6) running on 64-bit hardware. Both the OS and the Launcher are the most recent version. The problem occurs after launching the latest stable release and latest betas of Minecraft Java Edition.
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
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
macOS Mojave (10.14.6) and macOS Big Sur, running on 64-bit hardware. Both the OS and the Launcher are the most recent version. The problem occurs after launching the latest stable release and latest betas of Minecraft Java Edition.
Launcher process does not quit and becomes unresponsive after closing game in macOSMojave
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
relates to
MCL-17493
WorkaroundOccasionally, this issue can be fixed by quitting or force quitting the Minecraft Launcher process in the Activity Monitor. To do this:
- 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 (if you don't see the Minecraft Launcher, then this fix won't work for you)
- 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)
macOS Mojave (10.14.6) and macOS Big Sur, running on 64-bit hardware. Both the OS and the Launcher are the most recent version.
The problem occurs after launching the latest stable release and latest betas of Minecraft Java Edition.
Workaround
Occasionally, this issue can be fixed by quitting or force quitting the Minecraft Launcher process in the Activity Monitor. Todo this:
- 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
(if you don't see the Minecraft Launcher, then this fix won't work for you)- 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)
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)
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.
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
is duplicated by
is duplicated by
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
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.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
![[Helper] pine1needle](../../../data/avatars/users/41329.png){kind=small}
relates to
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
is duplicated by
Hi, and thanks for your report! This has actually already been reported, and is being tracked as MCL-17399.
Does MCL-17399 happen to describe your issue?
Hi, does MCL-17399 describe your issue? If it does, please see the Workaround in the description of that report for a potential (temporary) fix to your issue.
Does MCL-17399 describe your issue?
This issue is already being tracked at MCL-17399. If you want to, please consider voting for that issue.
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Oh thats an interesting bug. I had to close my launcher and reopen again using the activity monitor to resolve this issue . You can check the ticket MCL-17399
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
For anyone using the CLI method to launch the game, I've found that if I need to restart the app it doesn't work. The following is another bug/solution that will get you up and running if you need to restart the launcher:
I'm glad to see MCL-17399 is resolved, but after removing the workaround for that I'm unfortunately I'm still seeing this issue where `Minecraft Launcher` stops responding, such that trying to open `Minecraft.app` silently fails until I force quit the launcher. 
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCL-17399, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Can you attach logs from when the issue occurs?
The launcher's log? Where is that located?
The "launcher_log.txt" and "launcher_cef_log.txt" files in the "/Users/XXX/Library/Application Support/minecraft/" directory.
It's intentional for the launcher to remain open in the background while the game is running so that crashes can be caught by the launcher. However, I have recently started experiencing the issue where the launcher does not close after Minecraft is closed. This makes it impossible to re-launch the game until you manually force quit the unresponsive launcher. I am using macOS Catalina.
This is also an issue on Big Sur (11.2.1). Killing the launcher process in Activity Monitor fixes the issue.
Is this a thing as well again? Never had my computer heating up for Minecraft before.
MCL-12293This is also an issue with the BigSur 11.2.3 - On the new MacBook Air (M1). I don't believe finding a work around is a solution. I shouldn't have to quit Minecraft from the activity launcher every time I want to play.
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?
This issue occurred for me today using version 2.2.3964, so it still exists.
I'm glad to see
MCL-17399is resolved, but after removing the workaround for that I'm unfortunately I'm still seeing this issue where `Minecraft Launcher` stops responding, such that trying to open `Minecraft.app` silently fails until I force quit the launcher.I am constantly seeing this also. I'm using 12.2.1 Monterey.
I can confirm this issue still exists macOS 12.3.
Launcher: macOS 10.16.0 2.2.11104
Bootstrap: 1125
UI: 8898
If someone running into this bug can, immediately after encountering it, grab a launcher log file from their .minecraft folder and attach it here that would be very helpful in assisting us in getting to the bottom of what's going on right now.
So RIGHT after you run into the "not responding" state, open up your .minecraft folder and grab the launcher log, and attach it here please!
It just happened.
launcher_log-1.txt
Here too, yesterday night. Didn't notice it until I wanted to launch Minecraft again now this morning.
launcher_log.txt
Jørn Støylen the file you sent is from 26/03/2021.
Thanks for calling that out, Thomas A.
For context: Logs that are not current are not useful in helping to diagnose, and in fact can make it harder if it adds confusion as this one will have.
[Mojang] Donuts1000 Ho my bad i just understand what happened, the link in the comment is not the good one (even for my comment), but the file has been correctly uploaded to Jira
my file: launcher_log-1.txt
Jørn Støylen 's file: launcher_log-2.txt
Edit: I updated my initial message with the good link.
What I can say looking at these two log file is that there is a "PresenceHeartbeat" operation failing in both files at the end when the game process closes. Maybe the reason the launcher process doesnt exit.
Ahhh, nice that you found out. I thought it was very strange, because I was sure my file was current …
It happened again: I played yesterday night, and quit the game after disconnecting from the game. Tried starting Minecraft now, and the Minecraft Launcher is not showing up as a running app in the app switcher or in the dock, but it's listed as (Not Responding) in Activity Monitor.
I've attached another launcher log, this time I renamed to include the date in the filename to avoid confusion.
And again, as Thomas mentioned, there is a warning at the end that says:
launcher_log_2022-03-28.txt
Not sure if this is a different bug, but I still get crashes after closing Minecraft. Not sure if it makes a difference, but I am playing on Apple silicone (M1) and thereby running Minecraft java in emulation mode.
hs_err_pid47353.log
I am still having issues with this in 2.3.136
M1 MacBook Pro running macOS Monterey 12.3.1