Protocol-Examples
profiler
Protocol-Examples | profiler | |
---|---|---|
2 | 184 | |
8 | 1,103 | |
- | 1.7% | |
4.6 | 9.6 | |
7 months ago | 7 days ago | |
TypeScript | JavaScript | |
MIT License | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Protocol-Examples
-
Is Something Bugging You?
Exactly - that's what we've already built for web development at https://replay.io :)
I did a "Learn with Jason" show discussion that covered the concepts of Replay, how to use it, and how it works:
- https://www.learnwithjason.dev/travel-through-time-to-debug-...
Not only is the debugger itself time-traveling, but those time-travel capabilities are exposed by our backend API:
- https://static.replay.io/protocol/
Our entire debugging frontend is built on that API. We've also started to build new advanced features that leverage that API in unique ways, like our React and Redux DevTools integration and "Jump to Code" feature:
- https://blog.replay.io/how-we-rebuilt-react-devtools-with-re...
- https://blog.isquaredsoftware.com/2023/10/presentations-reac...
- https://github.com/Replayio/Protocol-Examples
-
Future-Proofing Web Scraping via JavaScript Runtime Heap Snapshots
Not _quite_ what you're describing, but Replay [0], the company I work for, _is_ building a true "time-traveling debugger" for JS. It works by recording the OS-level interactions with the browser process, then re-running those in the cloud. From the user's perspective in our debugging client UI, they can jump to any point in a timeline and do typical step debugging. However, you can also see how many times any line of code ran, and also add print statements to any line that will print out the results from _every time that line got executed_.
So, no heap analysis per se, but you can definitely inspect the variables and stack from anywhere in the recording.
Right now our debugging client is just scratching the surface of the info we have available from our backend. We recently put together a couple small examples that use the Replay backend API to extract data from recordings and do other analysis, like generating code coverage reports and introspecting React's internals to determine whether a given component was mounting or re-rendering.
Given that capability, we hope to add the ability to do "React component stack" debugging in the not-too-distant future, such as a button that would let you "Step Back to Parent Component". We're also working on adding Redux DevTools integration now (like, I filed an initial PR for this today! [2]), and hope to add integration with other frameworks down the road.
[0] https://replay.io
[1] https://github.com/RecordReplay/replay-protocol-examples
[2] https://github.com/RecordReplay/devtools/pull/6601
profiler
-
Long running tab (kiosk), 100% CPU
Probably your best bet is to use the Firefox Profiler once it starts hogging the CPU to try to see what it's doing. I'd be happy to take a look at the result although I don't have a lot of experience at diagnosing performance problems; hopefully the profile will make it obvious what's going on.
-
Slow Firefox Startup
I tried using the https://profiler.firefox.com/ and running with:
- Firefox Profiler
-
Definite tab bug affecting both Win/Linux intermittently
You can try to reproduce while taking a profile using the Firefox profiler, then share it in the #perf:mozilla.org room on Mozilla's Matrix instance.
-
Why does Firefox run slow
Run a profiling session for ~30 sec when you notice something is running slower than you expect, see https://profiler.firefox.com/. Share results here if you want help interpreting them.
-
Problems with Firefox non snap versions on Ubuntu 22.04?
Next time, send a SIGABRT to the main process (kill -6 $(pidof firefox)) and use the resulting backtrace (you will find a link to the crash report in about:crashes) to file a bug. A performance profile could be useful, but you'll need to know first what to capture. This seems like a graphics issue, so try the Graphics preset. Share a link to your report.
-
Dear Firefox, why are you so terrible at rendering Flutter web apps? It's like potato quality.
https://profiler.firefox.com will be useful if you can capture and share it to developers.
-
Webpages not loading or taking forever to load
If you can reproduce it in safe mode and a clean profile, capture a performance profile using the clean profile while trying to load a problematic webpage, don't remove any information from it, and share it here (although it's typically not easy for users to analyse them), or file a bug with it attached.
-
Firefox hangs on Facebook page
Next time, capture a performance profile using the Graphics preset, and kill the browser by entering kill -6 $(pidof firefox) in a shell. This will create a bug report (unless debian disables the crash reporter) that would indicate where Firefox is stuck at. You might need to use an official build to get useful results.
- AV1 Lagging Like Mad
What are some alternatives?
devtools - Replay.io DevTools
xkeysnail - Yet another keyboard remapping tool for X environment
puppeteer-heap-snapshot - API and CLI tool to fetch and query Chome DevTools heap snapshots.
old-reddit-redirect - Ensure Reddit always loads the old design
fxsnapshot - Query tool for Firefox heap snapshots.
rust-threadpool - A very simple thread pool for parallel task execution
puppeteer - Node.js API for Chrome
OpenH264 - Open Source H.264 Codec
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
wolvic - A fast and secure browser for standalone virtual-reality and augmented-reality headsets.
heaptrack - A heap memory profiler for Linux
vdpau-va-driver-vp9 - Experimental VP9 codec support for vdpau-va-driver (NVIDIA VDPAU-VAAPI wrapper) and chromium-vaapi