Closed Bug 1863557 Opened 4 months ago Closed 28 days ago

GPU process is disabled for android PGO profile generation

Categories

(Core :: Performance, defect)

defect

Tracking

()

RESOLVED FIXED
Performance Impact none

People

(Reporter: jnicol, Unassigned)

References

Details

Android PGO profile generation jobs are run with browser.tabs.remote.autostart = false. We still launch content processes, I assume because e10s being fully disabled isn't a supported configuration nowadays. But this prevents us from launching a GPU process, meaning we don't get profile data from the GPU process.

I think e10s is disabled in testing/profiles/unittest-required/user.js. On desktop that is then overridden here, but deliberately not so on Android. I presume that's simply because enabling it for desktop PGO runs predates e10s being enabled generally on Android.

I think the solution is to remove the override from desktop-specific profileserver.py, and instead set the pref to true in testing/profiles/profileserver/user.js, which is used for both desktop and Android.

This will be fixed by bug 1724089

Depends on: 1724089
Performance Impact: --- → none

Bug 1724089 has now landed

Status: NEW → RESOLVED
Closed: 28 days ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.