1

I force quit Google Chrome by right-clicking the app icon in the Dock and selecting Force Quit. That seemed to quit Chrome (absence of indicator under app icon). However, when I try opening Google Chrome, nothing happens. When I open the Force Quit window by using the keyboard shortcut,Option + Command + Escape, Google Chrome is present in the list.

At the same time, Google Chrome does not show up in ps output or in Activity Monitor app.

I think that Chrome is actually closed but that macOS thinks it's open. How do I convince macOS that Chrome is, indeed, closed?

I have just installed macOS Mojave.

  • Is that really force quit? I use cmnd+opt+esc to get to force quit. – Solar Mike May 14 at 6:16
  • It's possible that Chrome launches lots of processes, not all of which are killed by Force Quit. You may need to look for other names in Activity Monitor. Why do you need to Force Quit Chrome? If you have to do that regularly, then I'd say that's your bigger problem. – benwiggy May 14 at 7:57
  • @SolarMike Yes, the Force Quit dialog came up. – Alex Szatmary May 14 at 12:36
  • @benwiggy It’s possible that one of Chrome’s other processes was remaining. I wound up just rebooting so I can’t confirm. This was a one-time thing, Chrome just hung. – Alex Szatmary May 14 at 12:38
  • Did you try force quit the app via terminal ? kill <PID number of app> – Edd Growl May 14 at 12:47
1

From searching online, I think I may have run into an edge case. My best guess is that, having just installed Mojave, one of the many new permissions dialogs was generated but hidden behind another window. As I closed programs, some permissions dialogs appeared, including for Chrome. This doesn’t make much sense as a cause but it was related to a major system change so it’s my best guess.

I wound up resolving the issue by rebooting.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .