Closed Bug 1642772 Opened 4 months ago Closed 3 months ago

Identify processes by eTLD+1 for fission in Nightly (with pref flip) and in the profiler

Categories

(Core :: DOM: Navigation, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
mozilla80
Fission Milestone M6a
Tracking Status
firefox80 --- fixed

People

(Reporter: jesup, Assigned: jesup)

References

Details

(Whiteboard: [7/14] patch r+, ready to land)

Attachments

(2 files)

To make it easier for developers and Nightly testers to identify processes that are causing problems, name processes with the eTLD+1 instead of "Isolated Web Process".
Note: only on Nightly and then only if a pref is flipped.

Also, set the process name in the profiler to include the eTLD+1 so you can see the sitenames in the profiler tracks. This sitename will need to be sanitized out of profiles when urls are blocked.

Severity: -- → S3
Type: defect → enhancement
Priority: -- → P2

Tracking for Fission Nightly milestone M6a since Jesup already has patches up.

Fission Milestone: --- → M6a

There are some r+ patches which didn't land and no activity in this bug for 2 weeks.
:jesup, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(rjesup)

I'm going to land this after uplift, especially since we only care about Nightly for fission at the moment

Status: NEW → ASSIGNED
Whiteboard: [7/14] patch r+, ready to land
Pushed by rjesup@wgate.com:
https://hg.mozilla.org/integration/autoland/rev/129c67f10b2c
Add fission process renaming to eTLD+1 for Nightly (only) via a pref r=smaug,dveditz
https://hg.mozilla.org/integration/autoland/rev/f06874791ca4
name processes in the profiler with eTLD+1 r=gerald,dveditz
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
Flags: needinfo?(rjesup)
You need to log in before you can comment on or make changes to this bug.