All articles
TroubleshootingEmulatorSupport6 min

Android Emulator Crashing or Closing Mid-Match on Mac: What to Do, and in What Order

Updated on · The MACOS EMULATOR team

You are mid-match, and the game disappears. In MACOS EMULATOR, two different things can close: the game, inside Android, or the whole Android device, engine included. The launcher will not tell you why, and we will not guess here. Here is how to recognize one from the other, what to copy before relaunching, and what to send to support.

Did the game close, or the device?

Look at what is left on screen:

  • The window is still there, on the Android screen, without the game, with the toolbar beside it: the game closed. The Android device is still running.
  • The window is gone, and the toolbar with it: the device stopped. At the top of the launcher’s home screen, the device button goes back to “Start” and its dot to gray, at most about thirty seconds later: during a match, the launcher only reads the device’s state again every thirty seconds.

If the device does not even make it to the game, that is another topic: the guide to an Android emulator not starting.

The launcher does not say why

In both cases, the launcher shows no message. It sees that the game or the engine is no longer there, not what made it go. The messages in the “Something went wrong” window, such as “The device stopped while it was starting.”, only concern startup.

When the device stops, macOS sometimes shows its own window, saying that an application quit unexpectedly. It comes from macOS, not from the launcher. Take a screenshot of it before closing it, with Shift + Cmd + 3.

Before relaunching: copy the logs

The engine’s log starts from scratch every time the device starts. If you click Play again right after a stop, the new boot erases what the engine had written before stopping. Copy it first:

  1. 1Open Settings: the gear icon, at the top right of the launcher.
  2. 2In the Engine and storage section, on the Logs row, click “View…”.
  3. 3The Logs window opens on emulator.log, the engine’s log. Click “Copy”, then paste it into a note while you write to support.

Copy takes the end of the file, roughly its last 200 KB: the lines written just before the stop. Until then, relaunch nothing: not Play, not the device button, not the launcher itself, which, depending on your settings, may restart the device when it reopens. The guide to the emulator’s logs details the window and its three files.

If it is the game that closed, the device is still running and its log has not been cleared. Copy it anyway before relaunching the game. The launcher’s logs are those of the engine and the launcher, not Android’s: we cannot promise you they say why the game closed. That is for support to judge.

The performance report does not tell the story of a stop

The performance report measures six seconds of a match in progress. It does not tell what happened before. The only trace of a stop it can carry is the engine’s last fatal error, and it reads it from that same log: after a relaunch, it is the one from the new session, or none.

Support still asks for a report, whatever the symptom. Take it during your next match, while playing, from the toolbar. The guide to measuring FPS in an emulator explains how.

What to send to support

  1. 1The logs: in your customer area, the “Send a report” button, Logs field, then “Send the report”. They go out as an attached file, without being cut off.
  2. 2What you saw, in your own words: the game alone or the whole device, after how long playing, and whether it happens again every match.
  3. 3The screenshot of the macOS window, if it appeared.
  4. 4Your configuration: model, chip, memory and macOS version, from the Apple menu, then About This Mac.

The site’s guide says it about logs: “This is by far the single most useful piece of information for us.” If you changed the Memory or the Quality, say so too. The launcher itself warns about two settings: above your Mac class’s value, its Memory sheet says that “the game stutters and Android can close it mid-match”, and its Ultra warning mentions “possible crashes”. That is not a diagnosis: change nothing before sending your logs, and support will tell you whether to go back to the starting values. The guide to contacting support shows the three doors.

Then, relaunching

  • The game closed: click Play again, the device is still on. Performance mode, for its part, gave your Mac’s other apps their place back within the thirty seconds that followed.
  • The device stopped: click Play again. A session that did not end with the Power off button makes the next boot start cold, longer than usual, once. Let it finish.

And do not uninstall to “start clean”: Uninstall erases the logs along with everything else, and starting from scratch guarantees nothing. The guide to resetting the emulator says what each step erases.

Frequently asked questions

Why does my Android emulator close mid-match?

The launcher does not say, and we do not guess: it sees that the game or the device is gone, not why. The logs, copied before relaunching, are what support reads to find out.

How do I know whether the game or the emulator crashed?

If the window stays open on the Android screen, the game closed. If the window and the toolbar are gone, and the device button goes back to “Start”, the device stopped.

Why copy the logs before relaunching?

The engine’s log starts from scratch every time the device starts. Relaunching after a stop erases what the engine had written just before: Settings, Engine and storage, Logs, “View…”, then “Copy”, first.

Does the performance report show the crash?

No: it measures six seconds of a match in progress. The only trace of a stop it can carry, the engine’s last fatal error, disappears at relaunch along with the log it reads it from.

Should I reinstall the emulator if it crashes often?

Not before writing to support. Uninstalling erases the logs that say what happened. Send them first with “Send a report”, from your customer area.