| Summary: | Web Inspector: CPU Usage Timeline - graph extends past end of recording stop time, doesn't match overview graph | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | BJ Burg <bburg> | ||||
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | bburg, inspector-bugzilla-changes, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Local Build | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Attachments: |
|
||||||
Created attachment 408484 [details] [SCREENSHOT] Screenshot attached. STEPS TO REPRODUCE: - Load nfl.com - Open Web Inspector, load Timelines Tab, remove all instruments except CPU + JS & Events - Select CPU timeline - Reload - Stop the recording => Utilization graph is extended beyond where it is shown in the timeline overview. It seems to go to the point when Timeline overview stops scrolling because it received the recordingStopped message from the backend. I think it would be best to have it extend to the last received data point, like for JS&Events.