Identify processes by eTLD+1 for fission in Nightly (with pref flip) and in the profiler
Categories
(Core :: DOM: Navigation, enhancement, P2)
Tracking
()
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.
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Depends on D77924
Comment 3•5 years ago
|
||
Tracking for Fission Nightly milestone M6a since Jesup already has patches up.
Comment 4•5 years ago
|
||
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.
Assignee | ||
Comment 5•5 years ago
|
||
I'm going to land this after uplift, especially since we only care about Nightly for fission at the moment
Updated•5 years ago
|
Comment 7•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/129c67f10b2c
https://hg.mozilla.org/mozilla-central/rev/f06874791ca4
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Description
•