| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Can you please file a new bug with more details about what is broken here?
I support changing the ifdef to USE_BLINK in StartupTracingController, that seems like a straightforward and correct change.
I'm less clear on why we need to stop using IOSTracingController, and more worried about having partially-divergent startup paths. Where exactly are we creating the startup controller when USE_BLINK is true? What specifically goes wrong when we create the IOSTracingController here?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Can you please file a new bug with more details about what is broken here?
I support changing the ifdef to USE_BLINK in StartupTracingController, that seems like a straightforward and correct change.
I'm less clear on why we need to stop using IOSTracingController, and more worried about having partially-divergent startup paths. Where exactly are we creating the startup controller when USE_BLINK is true? What specifically goes wrong when we create the IOSTracingController here?
@rohi...@chromium.org thank you!
Created a new bug crbug.com/511304747
After CL crrev.com/c/7700720 Blink-based Chromium on iOS will crash when launching. The reason is that Perfetto has been initialized twice.
One is from `content/app/content_main_runner_impl.cc`, another is from `iOS/chrome/browser/tracing/iOS_tracing_controller.mm`.
As for iOS Blink, Perfetto is already initialized by the content layer, and the Perfetto is initialized first in the content layer.
After adding `IOSTracingController`, Perfetto is initialized again in `IOSChromeMainParts::PreCreateThreads`.
We have to choose one of them, and no matter which one we choose, we will diverge from another. I tried to use initialization from `IOSTracingController` first, but it is more complicated and found that it will be simpler to reuse the initialization from the content layer.
And I also confirm that we can generate the tracing report correctly, and can see tracing data from render, GPU process and network process.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Xiaobin CuiCan you please file a new bug with more details about what is broken here?
I support changing the ifdef to USE_BLINK in StartupTracingController, that seems like a straightforward and correct change.
I'm less clear on why we need to stop using IOSTracingController, and more worried about having partially-divergent startup paths. Where exactly are we creating the startup controller when USE_BLINK is true? What specifically goes wrong when we create the IOSTracingController here?
@rohi...@chromium.org thank you!
Created a new bug crbug.com/511304747
After CL crrev.com/c/7700720 Blink-based Chromium on iOS will crash when launching. The reason is that Perfetto has been initialized twice.
One is from `content/app/content_main_runner_impl.cc`, another is from `iOS/chrome/browser/tracing/iOS_tracing_controller.mm`.
As for iOS Blink, Perfetto is already initialized by the content layer, and the Perfetto is initialized first in the content layer.
After adding `IOSTracingController`, Perfetto is initialized again in `IOSChromeMainParts::PreCreateThreads`.
We have to choose one of them, and no matter which one we choose, we will diverge from another. I tried to use initialization from `IOSTracingController` first, but it is more complicated and found that it will be simpler to reuse the initialization from the content layer.
And I also confirm that we can generate the tracing report correctly, and can see tracing data from render, GPU process and network process.
@rohi...@chromium.org gentle ping~ Thanks!
lg, will stamp once the trybots are happy
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Xiaobin CuiCan you please file a new bug with more details about what is broken here?
I support changing the ifdef to USE_BLINK in StartupTracingController, that seems like a straightforward and correct change.
I'm less clear on why we need to stop using IOSTracingController, and more worried about having partially-divergent startup paths. Where exactly are we creating the startup controller when USE_BLINK is true? What specifically goes wrong when we create the IOSTracingController here?
Xiaobin Cui@rohi...@chromium.org thank you!
Created a new bug crbug.com/511304747
After CL crrev.com/c/7700720 Blink-based Chromium on iOS will crash when launching. The reason is that Perfetto has been initialized twice.
One is from `content/app/content_main_runner_impl.cc`, another is from `iOS/chrome/browser/tracing/iOS_tracing_controller.mm`.
As for iOS Blink, Perfetto is already initialized by the content layer, and the Perfetto is initialized first in the content layer.
After adding `IOSTracingController`, Perfetto is initialized again in `IOSChromeMainParts::PreCreateThreads`.
We have to choose one of them, and no matter which one we choose, we will diverge from another. I tried to use initialization from `IOSTracingController` first, but it is more complicated and found that it will be simpler to reuse the initialization from the content layer.
And I also confirm that we can generate the tracing report correctly, and can see tracing data from render, GPU process and network process.
@rohi...@chromium.org gentle ping~ Thanks!
Done
tvOS-rel-fyi build error is not related.
[iOS Blink] Use content layer Perfetto tracing instead
Guard IOSTracingController behind !USE_BLINK so the content layer
handles Perfetto initialization normally for iOS Blink, matching other
platforms.
Also fix StartupTracingController to use kCustomBackend when USE_BLINK
is enabled, so startup traces are actually collected.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |