Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
[ID: 1223084]
[ID: 1223086]
[ID: 1223031]
Platform
Platform>DevTools
Platform>DevTools>Performance
[ID: 1253656]
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
Design doc to be reviewed. [ID: 1223032]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223034]
[ID: 1223088]
View issue level access limits(Press Alt + Right arrow for more information)
Estimated effort
Request for new functionality
View staffing
Description
While analyzing a performance recording, it’s hard to compare other tracks to the flame chart if there are large call stacks. These call stacks take up a lot of vertical space and require a lot of scrolling up and down. To improve this, developers should be able to adjust the height of an expanded track, so that they can limit the view to focus on the most relevant sections while debugging.
Doc:https://docs.google.com/document/d/1GbTSiEotlsA4DFHB-bTvA0J3D7p7b9-ecf0uwcy5FpE/edit?usp=sharing