Closed Bug 1446574 Opened 6 years ago Closed 6 years ago

[meta] Remote profiling for GeckoView milestone 1

Categories

(Core :: Gecko Profiler, defect, P1)

Unspecified
Android
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: past, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [geckoview:p2])

This is the first milestone of the work for getting remote profiling for GeckoView working. The work includes:

Provide a new performance panel, only for Nightly and hidden by default, that works with remote debugging to capture profiles from Android devices running GeckoView.

The minimum GeckoView version will be dictated by getting platform fixes landed that unblock profiling. From then on any subsequent GeckoView version can be profiled by Firefox Nightly.

While the new panel can also be used for desktop profiling, the Gecko Profiler extension will remain the recommended workflow for desktop.

Constraints: Will only support symbolication for official builds. Local builds will be symbolicated in the next milestone.

User End Goals
- Keep recording profiles while trying to reproduce issues. Have a minimal-impact recording experience.
- Have a capturing methods that stays out of the way. Engineers expect affordances like shortcuts and responsive capturing experience.
Depends on: 1446945
Depends on: 1444124
Depends on: 1450233
Depends on: 1450709
No longer depends on: 1450709
Depends on: 1450709
No longer depends on: devtools-perfhtml
Depends on: 1453220
No longer depends on: 1453220
No longer depends on: 1350501
No longer depends on: 1371003
OS: Unspecified → Android
Whiteboard: [geckoview]
Depends on: 1477596
Depends on: 1471795
Depends on: 1479411
Depends on: 1484828
Whiteboard: [geckoview] → [geckoview:p2]
Depends on: 1457481
This is now fixed. Official Nightly Fennec + GeckoView builds can now be profiled using WebIDE and get full symbols, both for Gecko binaries and for Android system libraries.

Local Fennec + GeckoView builds do not get symbols yet. Implementing that is tracked in milestone 1.1, bug 1446575.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.