Some IPC marker payload fields are missing even though they have start and stop markers
Categories
(Core :: Gecko Profiler, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox99 | --- | fixed |
People
(Reporter: canova, Assigned: canova)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
I think we have two issues related to IPC marker missing fields. One reason that they are missing becasue we can't record the IPC markers when the threads are not profiled so they become incomplete markers. There is Bug 1709104 for that already.
But I've also seen cases where we have proper start/end markers for both send and recv but still fails to show the marker fields and marks them as "unknown" in the front-end. We should investigate why.
|
Assignee | |
Comment 1•2 years ago
|
||
So each IPC message consists of 5 markers. We correlate them in the front-end side to make a single marker per process. First and last markers are added from the thread that IPC is being sent/received. But the middle 3 markers are being added from the "IPC I/O Parent" and "IPC I/O Child" threads. Since we don't profile those threads by default, some fields are always "unknown" until we profile them. Since these threads are not really worth adding to our presets (due to very low activity) we should add those markers to the main threads instead.
|
|
Assignee | |
Comment 2•2 years ago
|
||
|
||
Updated•2 years ago
|
Pushed by canaltinova@gmail.com: https://hg.mozilla.org/integration/autoland/rev/84b3bfb0d17e Send the IPC markers in IPC I/O thread to the main thread if they are not profiled r=gerald
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Description
•