Closed
Bug 931959
(Frame-Rate-Drop-JS)
Opened 11 years ago
Closed 7 years ago
Frame Rate Drop Root Cause: JS
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: akratel, Unassigned)
References
Details
(Whiteboard: [User Story], [mockup])
User Story
As a web app developer, I would like to be able to identify JS code that causes frame rates to drop. Acceptance Criteria: * find in the recording where JS engine was linked to a frame rate slowdown * find int eh recording places where the browser spent a lot of time in the JS engine * Be able to drill down to see the actual JS function or line of code that was associated with the slowdown * Be able to distinguish from external slow down causes versus problems my own app is causing. In other words the recording should be tab specific or app specific (FxOS). Note: there are several scenarios that JS can cause slowdowns, we may want to break up this user story into the scenarios. For example: * TIme spent in JS engine is short, but subsequent graphics consumption is high * Time spent in JS engine is long, not necessarily associated with high graphics consumption. Visualization could be done via time-based flame chart where every frame is broken down into where the browser spends time.
As a web app developer, I would like to be able to identify JS code that causes frame rates to drop.
Acceptance Criteria:
* find in the recording where JS engine was linked to a frame rate slowdown
* find int eh recording places where the browser spent a lot of time in the JS engine
* Be able to drill down to see the actual JS function or line of code that was associated with the slowdown
* Be able to distinguish from external slow down causes versus problems my own app is causing. In other words the recording should be tab specific or app specific (FxOS).
Note: there are several scenarios that JS can cause slowdowns, we may want to break up this user story into the scenarios. For example:
* TIme spent in JS engine is short, but subsequent graphics consumption is high
* Time spent in JS engine is long, not necessarily associated with high graphics consumption.
Visualization could be done via time-based flame chart where every frame is broken down into where the browser spends time.
Reporter | ||
Updated•11 years ago
|
Flags: pm-scrub?
Reporter | ||
Updated•11 years ago
|
Component: Developer Tools → Developer Tools: User Stories
Reporter | ||
Updated•11 years ago
|
User Story: (updated)
Component: Developer Tools: User Stories → Developer Tools: Performance Tools (Profiler/Timeline)
Comment 1•7 years ago
|
||
I believe this is no longer relevant.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•