| Summary: | Web Inspector: CPU Usage Timeline - better resolution of installation source for repeated timers | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joseph Pecoraro <joepeck> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
CPU Usage Timeline - better resolution of installation source for repeated timers setInterval fire fire time: | * * * | range 1: |----------------------------------| => Timer Installed, Repeat of 2 => ~2 (the number of fires of this installed timer in range, with install location) range 2: |----------------------| => Timer Installed, No Repeat seen => ~1 (the number of fires of this installed timer in range, with install location) range 3: |------| => Timer Installed, No Repeat seen => ~1 (the number of fires of this installed timer in range, with install location) range 4: |---------------------| => No Installed, Repeat of 2 => ~2 (the number of fires of this installed timer in range, with fire location) range 5: |------| => No Installed, Fire happened once => nothing (we don't know where it was installed, or where if it is repeating) In case (4) we should be able to provide the install location since it was in the entire recording. We could have a map of all repeating timer installations in the whole recording so that we can provide a function name for these repeating timers lacking an installation point.