Adding proper component and OS label for more inputs on this as new Mac or formatted Mac laptop is not available as of now.

This seems to have something to do with composition and not the DevTools...

This is another Mac 10.12 issue, it seems. The problem goes away with --disable-gpu, so passing to the GPU team for triage.

>The problem goes away with --disable-gpu, so passing to the GPU team for triage

Not entirely, you cannot highlight elements using the inspector on hover or select the elements on the DOM tree in the elements tab. Which practically, makes our productivity reaching zero.

I think that comment #3 was made in error (maybe intended for a different bug).

ccameron@: Check out the bug linked at the top. It sounds like --disable-gpu fixed most of the problem for many people.

Instead of --disable-gpu, can you try the following flags
  --disable-mac-overlays
and also
  --disable-gpu-rasterization
Try them separately and together.

tingan87@, can you please update thread per c#7?

Just to update, I got a new MacBook Air OS version 10.12.4 and this worked fine and I was able to launch chrome from the terminal and devtool blue highlight was seen on mouse hovering over elements. Tested on chrome Dev version: 60.0.3107.4 and stable version: 58.0.3029.110.

Deleted: 713290.png 257 KB

	713290.png 257 KB View Download

Even though the title does not reveal it clearly: this bug is also about graphical glitches. (See “Original issue” mentioned by the reporter.)

On my Mac (Mac mini (end 2014)) I drew the following conclusions:

-   I updated the OS from 10.11 to 10.12.5, but that had no influence on the graphic problems
-   the problem is visible with Chrome v59
-   starting Chrome via spotlight (and not from a terminal) never revealed any graphic or other problems, even though --disable-gpu or any other custom command line arguments were not active (checked with chrome://version)
-   starting Chrome on the terminal without command line arguments resulted in graphic glitches on different web pages
    -   apart from graphic glitches, mouse clicks did not work on some web pages(!)
-   starting Chrome on the terminal with --disable-gpu-rasterization resolved the graphic glitches!
    -   the mouse interaction problems stayed, but the affected web pages changed in a seemingly non-determinable manner
-   the switch --disable-mac-overlays seemed to have no effect (neither with, nor without --disable-gpu-rasterization)
-   the switch --whatever-I-write had no effect either → it is hard to tell which command line arguments Chrome understands


I don’t understand why starting from the terminal and via spotlight is of any difference. Is there a way to start Chrome from the terminal like a “normal” start? Can I start “terminal-Chrome” from spotlight?

To me it seems that starting Chrome via spotlight either makes Chrome disable GPU rasterization automatically, or to do it in a different (working) manner. How can I investigate this better? :-o

Since we are unable to repro this, requesting ccameron@ for help in triaging this better and more inputs as per C#10.

Thanks for the feedback.

Could you please upload a copy of the output from "chrome://gpu" in both scenarios (from spotlight, and from command line while broken)?  Thanks!

Setting to Internals>GPU>Rasterization based on the comment in #10 that --disable-gpu-rasterization fixed the glitches.

I believe this is fixed in M60 (duplicate of isssue 711683). If you're able to, can you check whether this reproduces in Beta?