Just now while using Chrome with an infinite number of tabs and windows, it stopped responding with a colorful spinwheel. The computer is still working, but every other application moves 30x slower whereby every action I make will be delayed by ~2 seconds, even if its a simple click. I waited for about 10 minutes to unlag but its still the same.

I opened activity monitor and started quitting all Chrome subprocesses. After about 3 minutes, computer is completely fine now, but Chrome main process is still showing as not responding:

enter image description here

How do I investigate what's going wrong? And how can it be fixed?

(Btw, I remembered having a similar issue 2 months ago and I managed to fix that one after much googling, but I can't remember how I fixed it.)


2 Answers 2


My friend, ask yourself how deep you desire to know and how far you are willing to go. If you desire merely a working Chrome, reinstall it and hope that all will go better.

If you want more than that, then let us explore what tracing and profiling can tell us. You will need Xcode and need the command-line tools installed. If you have chrome still running, then pull up a Terminal, and let’s profile chrome for a minute when it starts beach-ballin’.

sudo sample $( pgrep Chrome ) 60 -f ~/Desktop/chrome.profile.txt

You can also use Instruments for the same:

sudo instruments -l 60000 -t Time\ Profiler -p $( pgrep Chrome )

You likely will spot something in there that takes up most of the time. Time now for trace. When you are ready, straight bust a dtruss on Chrome, to see the low level:

sudo dtruss -a -f -n Chrome 2> ~/Desktop/Chrome.trace.txt

Let it run for a minute. Then stop with CONTROL-C, as I recall, off the top of my head. Then examine that trace file!

Enjoy, and Good Yule,


  • I ran dtruss on the stuck Chrome for a couple of minutes and ctrlC it. This is the output: drive.google.com/file/d/16bueYrulbH23Loj6WO-esnTtjIM52xmU/… .
    – Pacerier
    Dec 14, 2017 at 11:20
  • For Chrome sample is it safe to post the output? In any case, how am I supposed to read it to see what has went wrong?
    – Pacerier
    Dec 14, 2017 at 11:21
  • Simply open the files we created on your desktop. Files we named chrome.profile.txt and chrome.trace.txt. Dec 14, 2017 at 12:11
  • Make sure to run those commands as root. Without the ‘sudo’ part, the output is meaningless given privilege restriction. Dec 14, 2017 at 12:14
  • Change end of dtruss line to read ‘> ~/Desktop/Chrome.trace.txt 2>&1’ Dec 14, 2017 at 12:17

This helped me! Chrome unfroze and is running perfectly now.


  • 2
    Answers on Ask Different need to be more than just a link. We expect answers to be self contained, since if your link goes down, your answer will be useless. Paraphrasing the source and including any relevant information in the answer will ensure it stays relevant. Also, please make it more clear how the procedure described in the linked page solves the specific problem described in the question.
    – nohillside
    Aug 8, 2018 at 19:51

You must log in to answer this question.

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