Closed
Bug 1163430
Opened 10 years ago
Closed 3 years ago
JS markers do not recognize console input as an entry point
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jsantell, Unassigned)
Details
(Whiteboard: [devtools-platform])
When recording, inserting this into the console:
`let i = 1000000; while (--i) { Math.pow(i,2) }`
We see a large dip in the FPS, but no JS markers. We should track these as valid JS entry points.
|
Reporter | |
Updated•10 years ago
|
Summary: JS Markers do not recognize console input as an entry point → [marker] JS Markers do not recognize console input as an entry point
|
||
Updated•10 years ago
|
Whiteboard: [devtools-platform]
|
||
Comment 1•9 years ago
|
||
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
Priority: -- → P3
Summary: [marker] JS Markers do not recognize console input as an entry point → JS markers do not recognize console input as an entry point
Version: 37 Branch → unspecified
|
||
Updated•7 years ago
|
Product: Firefox → DevTools
|
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 2•3 years ago
|
||
This report is related to the old DevTools profiler implementation, which has been removed. The Performance panel is now based on Firefox Profiler at https://profiler.firefox.com/
Closing as invalid
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•