profiler
profiler copied to clipboard
firefox-devtools
Firefox Profiler — Web app for Firefox performance analysis
## Description I use Firefox Profiler with [samply](https://github.com/mstange/samply), and to view the results in firefox profiler, I port forward the samply server to localhost. This used to work no problem...
While I was looking at a profile I encountered this error when I pressed the back button: ``` TypeError: can't access property "color", n[s] is undefined. ``` And devtools console...
When a line is selected, the path to the file has a contrast of 2.9:1, which is not accessible That's caused by the `opacity: 0.6` in https://github.com/firefox-devtools/profiler/blob/61a58948db3cae712b5688e181d46784dc7497aa/src/components/shared/TreeView.css#L150-L153 I find it...
This has been in my mind for some time. Whenever I want to profile something, the first thing I do is to switch to the flame graph from call tree...
Sometimes I've wanted to inspect profiles from the command line, without loading them in the web UI. Here's an experiment I've been working on, which creates a `pq` tool ("profile...
Known issues: - [ ] the interval in the profile info panel is shown with a time unit. - [ ] the stack chart tooltips show time units (but the...
[Main branch](https://main--perf-html.netlify.app/public/etegz8k5g139b8q7n74qfqv6z4ztb0nzvy051k0/calltree/?globalTrackOrder=0&thread=0&v=11) / [Deploy preview](https://deploy-preview-5589--perf-html.netlify.app/public/etegz8k5g139b8q7n74qfqv6z4ztb0nzvy051k0/calltree/?globalTrackOrder=0&thread=0&v=11)
We have files like `bin/l10n-sync.js` that have JSDocs in them, but apparently we are not checking them with `yarn ts` correctly. See my comment here: https://github.com/firefox-devtools/profiler/pull/5659#issuecomment-3498430787 It would be good...
(untested, I found this in my local tree)
Metadata
Owner
Metadata
Firefox Profiler — Web app for Firefox performance analysis