Open Bug 1823370 Opened 2 years ago Updated 11 days ago

[meta] Control the profiler using signals

Categories

(Core :: Gecko Profiler, enhancement, P3)

Product:
Core
Component:
Gecko Profiler
Type:
enhancement

Tracking

()

People

(Reporter: julienw, Unassigned)

References

(Depends on 5 open bugs, Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [fxp-profiler])

By being able to control the profiler by sending signals to the firefox process (to start and stop+capture), we could make it easier to capture a profile in these cases where the firefox' main process is frozen.

Indeed this would be a good feature to have. It's usually not easy to profile when Firefox is frozen.

Severity: -- → N/A
Priority: -- → P3
Flags: needinfo?(abrouwersharries)

Thoughts from discussion with julienw:

  • Dumping profile when stopping the profiler may be necessary if we have a "stuck" main thread, as the front-end won't be accessible.
  • Do we need to support kill-all, or can we rely on IPC to propogate the command to end the profiler.
  • Is it the main thread/process that is gathering all the data? What happens if there is an issue with that process?
Flags: needinfo?(abrouwersharries)
Assignee: nobody → abrouwersharries
Assignee: abrouwersharries → nobody
Keywords: meta
Summary: Control the profiler using signals → [meta] Control the profiler using signals
You need to log in before you can comment on or make changes to this bug.