Closed Bug 1709104 Opened 4 years ago Closed 3 years ago

When IPC profiling is enabled, we should capture all IPC markers regardless of which threads are profiled

Categories

(Core :: Gecko Profiler, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
99 Branch
Tracking Status
firefox99 --- fixed

People

(Reporter: mstange, Assigned: canova)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

To get IPC information, you currently have to profile the following threads:

  1. The source and the destination thread of the IPC message, to get start/stop timings.
  2. The threads "IPC I/O Parent" and "IPC I/O Child", to get various latency timings.
  3. For messages that go through PBackground, you also need the PBackground thread.

That's because the IPC information is captured in markers, which are inserted on various threads. The profile front-end can only display the information if those markers have been captured, and the markers are only captured if the threads are profiled.

It would be great to find a different solution to this that does not require the other threads to be profiled. For example, maybe we could associate all IPC information markers with the main thread instead.

Severity: -- → N/A
Priority: -- → P2
Assignee: nobody → canaltinova
Status: NEW → ASSIGNED
Attachment #9266115 - Attachment description: Bug 1709104 - Send the IPC markers in sender/receiver threads to the main thread if they are not profiled r?gerald → Bug 1709104 - Send the IPC markers in sender/receiver/background threads to the main thread if they are not profiled r?gerald
Pushed by canaltinova@gmail.com: https://hg.mozilla.org/integration/autoland/rev/76d6c7abf032 Send the IPC markers in sender/receiver/background threads to the main thread if they are not profiled r=gerald
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: