Open Bug 1592914 Opened 5 years ago Updated 2 years ago

[new popup] Consider using startProfiler from background.jsm.js for all situations

Categories

(DevTools :: Performance Tools (Profiler/Timeline), task, P2)

task

Tracking

(Not tracked)

People

(Reporter: julienw, Unassigned)

References

Details

With the current setup I believe we could use startProfiler [1] directly for all situations, including in a remote setup. Obviously for that setup if will be called by the actor.

The popup and devtools panel settings UI job is to change the preferences on the debugging target. Then startProfiler uses these preferences directly on the same running gecko.

Advantages:

  • we don't need to pass the options through the devtools protocol
  • when/if we move the settings to a separate page, the "start/capture" button could be a super simple app without react

Drawbacks:

  • need to manage backward compatibility

[1] https://searchfox.org/mozilla-central/rev/1fe0cf575841dbf3b7e159e88ba03260cd1354c0/devtools/client/performance-new/popup/background.jsm.js#173-194

Any opinion on this Greg ?

using a more direct captureProfile is more challenging given all the retrieving / symbolication mechanism. But because this happens only once the profiler runs, maybe we could accept loading more JS files for this state (?)

Priority: -- → P2
See Also: → 1701396
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.