You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frameTable has an innerWindowID column so that we can determine, per sample, whether that sample was relevant for a given page. This is what we use in the active tab view to hide samples from other tabs.
But the active tab view is going to be removed (#4997).
The replacement doesn't do any filtering of samples. The motivation for this was two-fold:
Firefox Desktop now puts separate origins into separate content processes ("Fission"), so by filtering processes, you also make sure that the remaining processes only contain relevant samples.
Even if code from different pages runs in the same process, anything within a process can be relevant to slow performance, so it's better to just show it all.
This means that the innerWindowID information in the frameTable will be unnecessary. We will need another way to know which process is relevant to which page (#5442), but with that fixed, we should just remove the innerWindowID column from the frameTable entirely.
The frameTable has an innerWindowID column so that we can determine, per sample, whether that sample was relevant for a given page. This is what we use in the active tab view to hide samples from other tabs.
But the active tab view is going to be removed (#4997).
The replacement doesn't do any filtering of samples. The motivation for this was two-fold:
This means that the innerWindowID information in the frameTable will be unnecessary. We will need another way to know which process is relevant to which page (#5442), but with that fixed, we should just remove the innerWindowID column from the frameTable entirely.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: