a805bb0151
This is a reland of commit972bef57b3No change was made. LUCI Bisection misdiagnosed this CL as the culprit of ASAN failures. Original change's description: > Reland "[tracing] Use trace thread for gpu process to initialize tracing" > > This is a reland of commit44d8036a9d> > Previous CL was reverted because PostDelayedTask is dropped when > Linux/ChromeOS sandboxing procedure stops the running thread. Such tasks > need to be reposted. There're several places that PostDelayedTask to the > trace_thread: > - Some are through the PerfettoTaskRunner, that can be tracked easily. > - One is directly posted by ConnectProducerSocketViaMojo, needs to be > special treated. > > This CL: > - For trace_startup.h/.cc, add option to start tracing using the > trace_thread, and set will_trace_thread_restart to true on linux and > chromeos. > - For perfetto_traced_process.h/.cc, postpone system tracing producer > socket connection to after sandbox entrance on linux & chromeos. > - For perfetto_task_runner.h/.cc, store delayed tasks and post them when > internal taks_runner is reset. > > Original change's description: > > [tracing] Use trace thread for gpu process to initialize tracing > > > > For non-zygote child gpu thread, start the trace thread in > > ContentMainRunnerImpl() directly. > > > > For zygote child gpu thread, start the trace thread in RunZygote after > > zygote fork and featurelist init. > > > > For Linux & ChromeOS, stop and restart the trace thread when entering > > sandbox. Restarting trace thread has a caveat that delayed tasks would > > will be lost unless we save them. > > > > This is [3/?] CL of enabling tracing prior to sandboxing. > > > > Bug: 380411640 > > Change-Id: I89fa94f63a709de0e3da4f8759098c9fff813bee > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6180639 > > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> > > Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org> > > Commit-Queue: Kramer Ge <fangzhoug@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1428704} > > Bug: 380411640, b/401194534 > Change-Id: I0f9172e48ee601f0236d84b0d8f784a11bd3d61a > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6462335 > Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org> > Commit-Queue: Kramer Ge <fangzhoug@chromium.org> > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> > Reviewed-by: Zhenyao Mo <zmo@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1451893} Bug: 380411640, b/401194534 Change-Id: I32d42c00b0645783f00898ddc5167d655d773246 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6495650 Commit-Queue: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Zhenyao Mo <zmo@chromium.org> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Auto-Submit: Kramer Ge <fangzhoug@chromium.org> Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/main@{#1453740}
This directory contains UI frameworks used to build various user interface features. This directory is not intended to contain UI features (such as a keyboard).