Issue metadata
Sign in to add a comment
|
Running Content Shell with --single-process no longer works with Mac |
||||||||||||||||||||||
Issue descriptionWhen running Content Shell with the --single-process command line option, I just get a blank window. I use single process for debugging (lldb). Caused by https://chromium-review.googlesource.com/c/chromium/src/+/681850
,
Feb 17 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ff4fe2c4f799b5c0272eb65daaa1f35877460f17 commit ff4fe2c4f799b5c0272eb65daaa1f35877460f17 Author: Robert Sesek <rsesek@chromium.org> Date: Sat Feb 17 01:11:30 2018 [Mac] Force a MessageLoop::TYPE_UI for the GPU thread in --single-process. A TYPE_DEFAULT MessageLoop was previously backed by a native MessagePump, but switched to a MessagePumpDefault in 8e6fc5fef9b85c3fb7888e57eab9bf343ec83cf6. Bug: 812572 , 753544 Change-Id: I49c53766067fb69642d5835668c066861d21803f Reviewed-on: https://chromium-review.googlesource.com/923584 Reviewed-by: Antoine Labour <piman@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#537490} [modify] https://crrev.com/ff4fe2c4f799b5c0272eb65daaa1f35877460f17/content/browser/gpu/gpu_process_host.cc
,
Feb 19 2018
Thank you for fixing this! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rsesek@chromium.org
, Feb 16 2018Labels: -Type-Bug M-66 Type-Bug-Regression
Status: Started (was: Assigned)