Closed
Bug 719530
Opened 12 years ago
Closed 11 years ago
Cleopatra front-end improvements
Categories
(Core :: Gecko Profiler, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: BenWa, Unassigned)
References
Details
(Whiteboard: [Snappy:P2])
Cleopatra is the front end used to visualize performance profiler collected by the built-in profiler: https://developer.mozilla.org/en/Performance/Profiling_with_the_Built-in_Profiler The front end needs: the jstree replacement: (1) Selection state (2) Support arrow key movement. Histogram improvements: (1) High selected samples in jstree, (2) Add time axis (3) Click on a sample to select in jstree Right overview bar: (1) Jump between unresponsive range (2) Show information about selected sample Profile: (1) Add a link to show the data dump (2) Add a button to file a bug by passing the data to the extension
Reporter | ||
Updated•12 years ago
|
Component: General → Gecko Profiler
QA Contact: general → gecko-profiler
Comment 1•12 years ago
|
||
Is there a place to suggest other improvements? There are some Shark front-end features that would be really nice to have in our built-in profiler...
Reporter | ||
Comment 2•12 years ago
|
||
If there non trivial and need backend changes I would suggest filing a new bug and making it block bug 71322. I worked on this bug over the weekend, only the following changes still need to be done: Histogram improvements: (1) High selected samples in jstree, (2) Add time axis (3) Click on a sample to select in jstree Right overview bar: (1) Jump between unresponsive range (2) Show information about selected sample It now works very well on Mac under the profiling branch.
Reporter | ||
Comment 3•12 years ago
|
||
i.e. bug 713227
Comment 4•12 years ago
|
||
I have no idea about backend changes. I'll file separate bugs.
Updated•12 years ago
|
Whiteboard: [Snappy:P2]
Reporter | ||
Comment 5•11 years ago
|
||
Most of these have been implemented in the latest version of cleopatra.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•