BenchRushTest. Play. Improve.
BenchRush → Troubleshooting center
Troubleshooting Center

Troubleshooting center

Start with the symptom you can reproduce. BenchRush helps you separate page focus, browser behavior, operating-system settings and hardware before you replace anything.

Choose the symptom

A key is missing, repeats or works only sometimesCheck focus, ordinary keys, repeat behavior, connection and whether the symptom follows the keyboard.One mouse click sometimes becomes twoRun deliberate single-click trials and separate hand timing, browser behavior and possible switch chatter.A controller stick moves while untouchedWatch browser-visible axis values, compare both sticks and repeat after reconnecting or calibrating.A pixel looks dark, bright or the wrong colorUse clean solid-color fields to separate screen content, dirt, reflections and a repeatable panel artifact.Browser Hz is lower or less stable than expectedCheck frame time, tab visibility, display mode, power state and repeated samples.The symptom does not fit one categoryUse the general input checklist and change one layer at a time.

Isolate the layer

  1. Reproduce one exact symptom. “Left click duplicates once every ten deliberate presses” is more useful than “the mouse is weird.”
  2. Confirm page focus and an ordinary input. Browser shortcuts, media keys and navigation buttons may be intercepted before a page sees them.
  3. Repeat the same test. A consistent pattern is more useful than a single miss or one lucky timing result.
  4. Change one software layer. Try another browser before changing ports, drivers and hardware at the same time.
  5. Change the connection or computer. If the symptom follows the device, the hardware hypothesis gets stronger. If it stays with one environment, inspect that environment.
  6. Escalate when the decision matters. Manufacturer diagnostics, firmware tools, warranty checks or lower-level utilities are the right final step when you need a hardware conclusion.

What browser evidence can and cannot prove

A page can show that an event reached JavaScript, that a controller axis is offset in the Gamepad API, or that animation callbacks arrived at a certain cadence. It cannot inspect switch contacts, raw HID packets, internal firmware state or the physical pixels of your display. BenchRush deliberately keeps those boundaries visible.

Keep a small test record

For intermittent faults, write down the browser, connection type, test result and whether the symptom repeats on another machine. Four short observations can be more useful than twenty uncontrolled tests. For BenchRush benchmark scores, local history stays in this browser and can be exported from PlayerScore.

Start with a live test

Open all browser tests → · Browse all interpretation guides → · See exactly what the browser can measure →