https://github.com/masonm/reproduce_chromedriver_bug
Reproduce CPU throttling bug with Chromedriver
https://github.com/masonm/reproduce_chromedriver_bug
Last synced: 4 months ago
JSON representation
Reproduce CPU throttling bug with Chromedriver
- Host: GitHub
- URL: https://github.com/masonm/reproduce_chromedriver_bug
- Owner: MasonM
- Created: 2020-09-27T03:18:28.000Z (almost 6 years ago)
- Default Branch: main
- Last Pushed: 2020-09-27T03:23:47.000Z (almost 6 years ago)
- Last Synced: 2025-05-24T01:47:44.315Z (about 1 year ago)
- Language: JavaScript
- Homepage: https://bugs.chromium.org/p/chromedriver/issues/detail?id=3613
- Size: 8.79 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Overview
This is a minimal reproducible example of a bug with Chromedriver where CPU throttling doesn't work after calling `Emulation.setCPUThrottlingRate()` via the Chrome DevTools Protocol.
# Usage
Run `npm ci` to install dependencies (including Chromedriver) and run the example via `node index.js `, with `` replaced with the CPU throttle rate. The example will load the Wikipedia homepage and then dump out navigation timing metrics, and write a verbose log file to `log.txt`. Try varying the throttle rate and notice it has no effect on the reported metrics.