What causes GPU-bound frames you can't diagnose from the CPU profiler?

The game is GPU-bound — overdraw, expensive shaders, too many draw calls — but the CPU profiler shows idle time, so the real cost is invisible there.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Profile GPU Bottlenecks With a Frame Debugger

Quick answer: Use a frame debugger or GPU profiler to capture a frame, inspect draw calls and shader cost, and cut overdraw, draw calls, and expensive passes.

When the CPU is idle but the frame is slow, the GPU is the bottleneck. A frame capture shows where. Here is how to use it.

How to fix it

1. Capture a frame

Use the frame debugger or a GPU capture tool to record one frame and step through its draw calls in order.

2. Find the expensive passes

Identify overdraw-heavy transparencies, costly shaders, and excessive draw calls that dominate GPU time.

3. Cut and re-measure

Reduce overdraw, batch draw calls, and simplify shaders, then recapture to confirm the GPU frame shrank.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.