New debug logs and video
https://drive.google.com/open?id=1hYOYAVdlqwI3BsNBfNeP0KfFTRmrBdcA

On video in the beginning we can see how it's happening. And when re-launching with 
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --no-sandbox --disable-extensions --disable-plugins --incognito --enable-logging --v=1
It's not happening.

I suspect Adblock and Honey extensions then, 
And additionally see 

[60008:775:0905/160456.260598:VERBOSE1:gpu_init.cc(232)] gl::init::InitializeGLNoExtensionsOneOff failed
...
[60008:775:0905/160456.623294:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
...
[60004:11779:0905/160456.631777:ERROR:browser_gpu_channel_host_factory.cc(132)] Failed to launch GPU process.
[60004:775:0905/160456.631864:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.

Checking without extensions, as well as with --disable-gpu

From the crash data I could see renderer hang, which is hard to go on.

It would be really valuable to be able to have reliable repro steps. Is it possible to gather more data about how this occurs.

Also would it be possible to post chrome://gpu/ results here?

Thank you.

I am able to enter this state pretty reliable while running the Lastpass and UBlock Origin extensions.

What can I do to provide useful logs?

++ GPU log and it continues to crash on 70:

Deleted: gpu (1).html 52.4 KB

gpu (1).html 52.4 KB View Download

mac triage: over to ccameron@ for mac gpu

Does this bug go away if you enable "Viz Display Compositor (OOP-D)" in about:flags?

I think this went through gpu triage in #5 ... If that flag doesn't fix this, we'll need repro steps.

Enabled the flag (in about:flags) and relaunched without using the terminal command in #3 - after about 47 minutes of browsing (using ublock origin / Lastpass extensions) the behavior started again.

Pages would trigger logging on my server (urls were being hit, just no rendering in the browser)

Using 15" Macbook Pro (2016) running High Sierra that is an enterprise build.

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.